test-one
Skill1 starsChanged 3 months agoMITView on GitHub
Run tests for a specific agent or module by name
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- check-envSkill
- pipelineSkill
- run-agentSkill
- sdlc-initSkill
- sdlc-reviewSkill
- sdlc-statusSkill
- test-allSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 10
Run tests for one specific module.
- Very specific: line 35
If $ARGUMENTS does not match any shorthand above, also try matching as a literal filename under tests/ (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Run Single Test File
Run tests for one specific module. The user specifies the target via $ARGUMENTS.
Test file mapping
| Shorthand | Test file |
| company | tests/test_company_agent.py |
| job | tests/test_job_agent.py |
| match | tests/test_match_agent.py |
| optimizer | tests/test_resume_optimizer.py |
| excel | tests/test_excel_store.py |
| acceptance | tests/test_acceptance.py |
| ai-quality | tests/test_ai_quality.py |
| ats | tests/test_ats_matcher.py |
| exception | tests/test_exception_classification.py |
| gemini-cache | tests/test_gemini_pool_cache.py |
| gemini-retry | tests/test_gemini_pool_retry.py |
| injection | tests/test_prompt_injection.py |
| run-summary | tests/test_run_summary.py |
| prompts | tests/test_shared_prompts.py |
| workday | tests/test_workday_url.py |
Instructions
- Parse
$ARGUMENTSto determine which test file to run. If empty or invalid, list available test targets and ask the user to pick one. - If
$ARGUMENTSdoes not match any shorthand above, also try matching as a literal filename undertests/(e.g.test_match_agentortest_match_agent.py) before failing. - Run the test:
source venv/bin/activate && python -m pytest tests/<test_file>.py -v 2>&1 - Summarize results. If any test fails, briefly explain the failure cause.
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.

