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.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

This Claude skill establishes a comprehensive framework for development workflow standards, ensuring high code quality through Test-Driven Development (TDD), strict branching protocols, and automated verification. It streamlines the software development lifecycle by enforcing consistent commit standards and rigorous testing requirements for every code change, making it an essential tool for maintaining project integrity and technical excellence.

Use Cases

  • Feature Implementation: Automatically apply standardized testing and branching rules when developing new project features to ensure consistency.
  • Bug Fixing with TDD: Guide the debugging process by enforcing a 'test-first' approach, ensuring that every fix is verified and prevents future regressions.
  • Git Workflow Management: Maintain a clean and organized repository history by following GitHub-Flow, including proper fetching, branching, and conflict assessment.
  • Pre-PR Verification: Perform automated type checks and test suite executions before completing changes to guarantee that code meets all quality benchmarks.
namedevelopment-workflow-standards
descriptionDevelopment 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 origin then branch from origin/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 test and bun run typecheck before completing changes.