Seed4j:test Module
Testing & Qualityseed4j:test-moduleSeed4j:test Module is an Agent Skill for testing & quality published in the seed4j/seed4j repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Identify a Seed4J test application using a given module, then generate and test it via /seed4j:test-app
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/seed4j/seed4j/blob/HEAD/.claude/skills/test-module/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/seed4j-test-module, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Test Module Skill
Find the CI test application that exercises a given Seed4J module, then test it.
When to use
Use /test-module <module-slug> to verify that a specific Seed4J generator module produces compilable, testable code.
Example: /test-module spring-boot-kafka, /test-module vue-core
Arguments
$ARGUMENTS contains the module slug to test (e.g. spring-boot-kafka, datasource-postgresql).
If no argument is given, ask the user which module they want to test.
Steps to follow
Step 1 — Find the CI test application that contains the module
Read tests-ci/generate.sh and identify which $application block calls apply_modules with the target module slug.
Rules:
- Prefer the simplest application that includes the module (e.g.
spring-bootoverfullapp). - If the module only appears inside a shared function (
spring_boot,spring_boot_mvc,cucumber_with_jwt, etc.), any application that calls that function qualifies — again prefer the simplest one. - If the module does not appear anywhere in
generate.sh, stop and tell the user: the module is not yet registered in CI and needs to be added totests-ci/generate.shbefore it can be tested this way.
Step 2 — Delegate to /test-app
Once the application name is identified, run /test-app <app-name> to generate the project, compile it, and run its tests.