sova-test
Skill3 starsChanged 5 days agoApache-2.0View on GitHub
Run tests and linter for the current project until all issues are fixed.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- dashboard-designSkill
- database-patternsSkill
- design-systemSkill
- design-tasteSkill
- issue-templateSkill
- sova-address-prSkill
- sova-after-mergeSkill
- sova-agent-readinessSkill
- sova-audit-instructionsSkill
- sova-debugSkill
- sova-develop-explainSkill
- sova-develop-fullSkill
- sova-developSkill
- sova-extract-knowledgeSkill
- sova-find-taskSkill
- sova-health-auditSkill
- sova-ingest-reviewSkill
- sova-integrate-prSkill
- sova-issueSkill
- sova-new-featureSkill
- sova-optimize-knowledgeSkill
- sova-prSkill
- sova-rearrange-commitsSkill
- sova-researchSkill
- sova-review-fullSkill
- sova-review-prSkill
- sova-reviewSkill
- sova-simplifySkill
- sova-specSkill
- sova-standupSkill
- sova-statusSkill
- sova-update-docsSkill
- testing-patternsSkill
- visual-auditSkill
- dashboard-designSkill
- database-patternsSkill
- design-tasteSkill
- issue-templateSkill
- testing-patternsSkill
- visual-auditSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run tests and linter, fixing issues iteratively until everything passes.
- Distinctive: line 15
If unclear, check git diff --name-only to see which modules have changes.
- Very specific: line 19
Run the project's lint command: make lint
- Very specific: line 28
Run the project's test command: make test
- Very specific: line 47
After tests pass: Run the sova-review skill to self-review before pushing
- Very specific: line 48
Full workflow: Use the sova-develop-full skill for the complete develop-test-review-pr cycle
- Distinctive: line 52
Always fix linter issues before running tests
- Distinctive: line 53
After fixing issues, re-run to verify the fix
- Distinctive: line 56
NEVER use emojis in any output
≈ “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
Test Runner
Run tests and linter, fixing issues iteratively until everything passes.
Instructions
Step 1: Identify the Scope
Determine what to test from the arguments provided when this skill is invoked or the current directory.
If unclear, check git diff --name-only to see which modules have changes.
Step 2: Run Linter
Run the project's lint command: make lint
If linter fails:
- Analyze the errors
- Fix the code issues
- Re-run until it passes
Step 3: Run Tests
Run the project's test command: make test
If tests fail:
- Analyze the test failures
- Fix the code or tests as needed
- Re-run until they pass
Step 4: Scout Check
While fixing test or lint failures, scan each touched file for pre-existing issues: flaky test patterns, stale imports, dead code. Fix them alongside the failures. Keep scout fixes small and low-risk.
Step 5: Iterate
Repeat Steps 2-4 until both linter and tests pass completely.
Cross-References
- After tests pass: Run the
sova-reviewskill to self-review before pushing - Full workflow: Use the
sova-develop-fullskill for the complete develop-test-review-pr cycle
Rules
- Always fix linter issues before running tests
- After fixing issues, re-run to verify the fix
- Continue iterating until both pass
- Report final status when everything is green
- NEVER use emojis in any output
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.

