test-discipline Skill
Update tests when changing APIs — no exceptions Published by microsoft in frontier-agentic-devops-rvas.
Decision snapshot
Is this a fit?
Testing, Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is test-discipline Skill?
Update tests when changing APIs — no exceptions Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Testing use cases
- Documentation use cases
Declared skill metadata
- Source file: .squad/templates/skills/test-discipline/SKILL.md
Compatibility and setup
- Install or run with Copy skill directory
When to use test-discipline Skill
- Use it for testing.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/frontier-agentic-devops-rvas
- Skill file: .squad/templates/skills/test-discipline/SKILL.md
What it does
Update tests when changing APIs — no exceptions
Skill instructions
Context When APIs or public interfaces change, tests must be updated in the same commit. When test assertions reference file counts or expected arrays, they must be kept in sync with disk reality. Stale tests block CI for other contributors. Patterns - API changes → test updates (same commit): If you change a function signature, public interface, or exported API, update the corresponding tests before committing - Test assertions → disk reality: When test files contain expected counts (e.g., EXPECTEDFEATURES, EXPECTEDSCENARIOS), they must match the actual files on disk - Add files → update assertions: When adding docs pages, features, or any counted resource, update the test assertion array in the same commit - CI failures → check assertions first: Before debugging complex failures, verify test assertion arrays match filesystem state Examples ✓ Correct: - Changed auth API signature → updated auth.test.ts in same commit - Added distributed-mesh.md to features/ → added 'distributed-mesh'
Verified compatibility and discovery
Frequently asked questions
What is test-discipline?
test-discipline is a open-source AI agent skill with Copy skill directory. Update tests when changing APIs — no exceptions
Who is test-discipline best for?
test-discipline is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows.
How do I install test-discipline?
Install or run test-discipline using Copy skill directory. Check test-discipline for the latest setup command.
Is test-discipline actively maintained?
test-discipline may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
