From Gatling
Find an existing Gatling project, detect language and build tool used
How this skill is triggered — by the user, by Claude, or both
Slash command
/Gatling:gatling-detect-existing-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Search inside the current working directory, for a directory containing:
Search inside the current working directory, for a directory containing:
pom.xml file, with io.gatling:gatling-maven-plugin plugin (Maven project)
kotlin-maven-plugin plugin, language is Kotlinscala-maven-plugin plugin, language is Scalabuild.gradle or build.gradle.kts file, with io.gatling.gradle plugin (Gradle project)
kotlin plugin, language is Kotlinscala plugin, language is Scalabuild.sbt file with, with io.gatling:gatling-sbt plugin (sbt project)
package.json file, with @gatling.io/cli dependency (npm project)
typescript dependency, language is TypeScriptIf nothing matches, there is no existing Gatling project here.
npx claudepluginhub gatling/gatling-ai-extensions --plugin gatlingDetects project type, package manager, and monorepo structure. Returns correct commands for test/build/lint/dev. Run at project initialization and cache results in state. Use before running any build/test commands.
Detects programming language, framework, build tools, and test commands for any project. Run via /detect-language or ask "what language is this project?".
Detects the project's build system (npm, yarn, pnpm, pip, poetry, gradle, maven, cargo, go, make) and runs build/test commands. Useful for automating project setup and continuous integration.