test-integration-docker
Skill1 starsChanged 9 months agoApache-2.0View on GitHub
Run comprehensive integration tests using real skills (Vercel, Anthropic, Expo) in a Docker container. Managed via Makefile for standard lifecycle control.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/tech-stack.mdcCursor rule
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Verify Docker is running.
- Very specific: line 15
Run make -C integration_tests test in the project root.
- Very specific: line 17
Use make -C integration_tests clean if needed to prune images.
- Distinctive: line 23
Ensure the Docker daemon is active, then execute the following command from the project root to build the image and run the full test suite:
- Distinctive: line 51
All integration scenarios pass.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Integration Testing with Docker & Real Skills
This skill executes integration tests in a containerized environment using actual skill repositories from the community. It uses a Makefile to manage the build and test lifecycle.
Workflow Checklist
- Step 1: Environment Readiness
- Verify Docker is running.
- Step 2: Execute Tests
- Run
make -C integration_tests testin the project root.
- Run
- Step 3: Lifecycle Management
- Use
make -C integration_tests cleanif needed to prune images.
- Use
Detailed Instructions
1. Run Integration Tests
Ensure the Docker daemon is active, then execute the following command from the project root to build the image and run the full test suite:
make -C integration_tests test-verbose2. Standard Makefile Targets
You can also use the Makefile directly for granular control:
Build the image only
make -C integration_tests buildClean up images
make -C integration_tests cleanSuccess Criteria
- Docker image builds successfully with
gitandmakeinstalled. cafCLI is linked and available in the container.- Real-world skills are cloned from GitHub (Vercel, Anthropic).
caf skills addsuccessfully installs these real skills.- All integration scenarios pass.
Scenarios Covered
- CLI Health: Version and help checks.
- Real-World Skills (Vercel): Clones
vercel-labs/agent-skillsand installs skills likeweb-design-guidelines. - Real-World Skills (Anthropic): Clones
anthropics/skillsand installs document skills. - Subagent Verification: Lists available subagents in the clean container.
- Multi-Agent Matrix: Tests are executed for both
Claude CodeandCursoragents. - Scope Isolation: Tests are executed for both
projectandglobalscopes, verifying that global installations do not leak into the project'spackage.json.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

