test-discipline Skill
Testing practices for behavior-focused, refactor-resistant tests. Use when implementing features or fixing bugs to ensure tests verify intent through public interfaces. Also use when adding regression tests after bug fixes. Consulted by the implement agent during coding and by the review agent when validating test qual Published by microsoft in devsquad-copilot.
What is test-discipline Skill?
Testing practices for behavior-focused, refactor-resistant tests. Use when implementing features or fixing bugs to ensure tests verify intent through public interfaces. Also use when adding regression tests after bug fixes. Consulted by the implement agent during coding and by the review agent when validating test qual Published by microsoft in devsquad-copilot. 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.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Design and media
- Writing
- Testing use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use test-discipline Skill
- Use it for testing.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/test-discipline/SKILL.md
What it does
Testing practices for behavior-focused, refactor-resistant tests. Use when implementing features or fixing bugs to ensure tests verify intent through public interfaces. Also use when adding regression tests after bug fixes. Consulted by the implement agent during coding and by the review agent when validating test qual
Skill instructions
Test Discipline Philosophy Tests verify behavior through public interfaces, not implementation details. Code can change entirely; tests should not break unless behavior changes. A good test reads like a specification. Use TDD strategically, not dogmatically. The goal is high-quality tests that verify intent — the ordering of when tests are written is a means to that end, not the end itself. When to Write Tests First Test-first (red-green-refactor) works best when: - Fixing a bug: Write a test that reproduces the bug before fixing it. The test must fail BEFORE the fix and pass AFTER. If the bug is not reproducible via automated test (race condition, environment-specific), document why and what alternative evidence proves the fix. - Behavior is unclear: The test forces you to define expected behavior precisely before writing code. - Working on a well-defined interface: The contract is clear and the test is straightforward to write. When to Write Tests After (or Interleave) Design-first-t
Explore related resources
Frequently asked questions
What is test-discipline?
test-discipline is a open-source AI agent skill with Copy skill directory. Testing practices for behavior-focused, refactor-resistant tests. Use when implementing features or fixing bugs to ensure tests verify intent through public interfaces.
Who is test-discipline best for?
test-discipline is best for reusing agent instructions, scripts, and references, testing workflows, design and media workflows, writing 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.
Auto-fetched from GitHub.
