development-workflow-standards
Development process rules for this project including testing, branching, and commit standards. Use when implementing features, fixing bugs, or making any code changes.
When & Why to Use This Skill
This Claude skill serves as an automated guardian for project-specific development workflows, ensuring all code changes adhere to strict testing, branching, and commit standards. By enforcing Test-Driven Development (TDD), GitHub-Flow, and rigorous pre-PR verification, it minimizes technical debt and streamlines the path from local development to production-ready pull requests.
Use Cases
- Feature Implementation: Automatically apply project-specific branching rules and testing requirements when building new modules.
- Bug Fixing with TDD: Guide the development process by ensuring a failing test is written and verified before implementing any fixes.
- Pre-PR Quality Assurance: Perform automated conflict assessments and run comprehensive test/type-check suites before submitting code for review.
- Workflow Standardization: Maintain team-wide consistency by enforcing unified commit standards and origin-based branching strategies.
| name | development-workflow-standards |
|---|---|
| description | Development process rules for this project including testing, branching, and commit standards. Use when implementing features, fixing bugs, or making any code changes. |
Development Workflow Standards
Refer to development-workflow-standards.md for detailed rules.
Key Rules
- Testing with code changes: Always update or add tests. Code without tests is incomplete.
- TDD for bug fixes: Write a failing test first, then implement the fix.
- GitHub-Flow: Always
git fetch originthen branch fromorigin/main. - Conflict assessment: Before PR, check conflicts with latest main. If severe, propose re-implementation.
- Never merge PRs: Merging is always the user's decision.
- Verification: Run
bun run testandbun run typecheckbefore completing changes.