scaffold_tests
Skill3 starsChanged 2 months agoMITView on GitHub
Generates unit and regression test files for existing code. Creates "Happy Path", "Edge Case", and "Error" test stubs.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- krishnakanthb13/antigravity_global_skillsedited, first seen Jul 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- krishnakanthb13/antigravity_global_skills★ 50100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository46 other files it gives its agents.
- agy-customizationsSkill
- antigravity-guideSkill
- api-and-interface-designSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- code-review-and-qualitySkill
- code_reviewSkill
- code-simplificationSkill
- context-engineeringSkill
- create_launcherSkill
- create_skillSkill
- daily_logSkill
- debugging-and-error-recoverySkill
- debug_issueSkill
- deprecation-and-migrationSkill
- document_apiSkill
- documentation-and-adrsSkill
- enhance_uiSkill
- frontend_designSkill
- frontend-ui-engineeringSkill
- generate_release_imageSkill
- git-workflow-and-versioningSkill
- idea-refineSkill
- idea_to_actionSkill
- impeccableSkill
- incremental-implementationSkill
- list_featuresSkill
- open_source_prepSkill
- optimize_codebaseSkill
- performance-optimizationSkill
- permissioned-githubSkill
- planning-and-task-breakdownSkill
- release_helperSkill
- repo_infographicSkill
- security-and-hardeningSkill
- security_auditSkill
- shipping-and-launchSkill
- software_architectureSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- test_runnerSkill
- ui_ux_pro_maxSkill
- update_docsSkill
- using-agent-skillsSkill
- using-ui-stackSkill
- web_performance_optimizationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to automatically generate test suites for your code, ensuring functionality is locked in.
- Very specific: line 17
Use view_file to analyze the source code.
- Very specific: line 18
Use write_to_file to create the test file.
- Distinctive: line 37
Write the test file with three specific sections:
- Distinctive: line 50
Test-Driven Development (TDD): Write failing test FIRST, implement minimal code to pass, refactor after green.
- Distinctive: line 51
Behavior-Driven Testing: Test behavior, not implementation details.
- Very specific: line 52
Factory Pattern: When scaffolding tests, create data factory functions (e.g., getMockUser(overrides)) that provide sensible defaults but …
- Distinctive: line 53
Mocking Strategies: Use factory functions to mock entire modules or specific hooks when scaffolding tests to isolate the unit under test.
≈ “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
Scaffold Tests
Use this skill to automatically generate test suites for your code, ensuring functionality is locked in.
Inputs
- Target File: The source code specific to test.
- Test Runner: (Optional) Jest, Pytest, etc.
Tooling Strategy
- Use
view_fileto analyze the source code. - Use
write_to_fileto create the test file.
Workflow
1. Context Analysis
- Target: Analyze the open file or the specified module (e.g.,
utils.py,auth.js). - Framework Detection: Determine the project's test runner (Jest, PyTest, Mocha, Unittest). If none, suggest the most lightweight option suitable for the user's legacy hardware.
2. Test Strategy
Plan the test coverage:
- Unit Tests: Isolated tests for individual functions/classes.
- Regression Tests: Tests that ensure specific bugs (fixes) don't reappear.
- Naming Convention: Standardize names (e.g.,
[filename].test.jsortest_[filename].py).
3. Generation (The "Safety Net")
Write the test file with three specific sections:
- Happy Path: Standard inputs produce standard outputs (The "It works" check).
- Edge Cases: Nulls, empty strings, zeros, huge numbers (The "Robustness" check).
- Error Handling: Invalid inputs trigger the expected error messages (The "Security" check).
4. Output
- Save the file to a
tests/directory or alongside the source code (based on project convention). - Prompt the user to run them using
/run_tests.
Advanced Testing Patterns
- Test-Driven Development (TDD): Write failing test FIRST, implement minimal code to pass, refactor after green. Never write production code without a failing test.
- Behavior-Driven Testing: Test behavior, not implementation details. Focus on public APIs and business requirements. Use descriptive test names that describe the behavior.
- Factory Pattern: When scaffolding tests, create data factory functions (e.g.,
getMockUser(overrides)) that provide sensible defaults but allow tests to override specific properties. This keeps tests DRY and maintainable. - Mocking Strategies: Use factory functions to mock entire modules or specific hooks when scaffolding tests to isolate the unit under test.
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.