dqx-phase-commit

Orchestrate TDD, quality gates, and conventional commits for implementation phases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nampham2/dqx --skill dqx-phase-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dqx-phase-commit
Source: https://github.com/nampham2/dqx/tree/main/.opencode/skills/dqx-phase-commit
Command: npx skills add https://github.com/nampham2/dqx --skill dqx-phase-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end implementation phases across TDD, quality gates, and structured commits is often manual, error-prone, and hard to reproduce. This skill provides a repeatable orchestration that ties together individual phase skills into a single, auditable workflow.

Core Features & Use Cases

  • Orchestrates Phase execution by sequencing TDD, quality gate, and conventional commit steps.
  • Provides a repeatable template for implementing phases per a given implementation guide.
  • Generates progress reports and ensures gating criteria are met before committing and moving forward.

Quick Start

Invoke the phase-commit skill to automate a complete implementation phase from TDD to commit using your implementation guide.

Frequently Asked Questions about dqx-phase-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate TDD cycles, quality gates, and conventional commits together?

Automate TDD cycles, quality gates, and conventional commits together by orchestrating them into a single phase execution workflow. This coordinates tests, quality checks, and structured commits sequentially with progress reporting to ensure gating criteria are met before moving forward.

What is the best way to coordinate end-to-end implementation phases in a software project?

Coordinate end-to-end implementation phases by using an orchestration template that sequences test-driven development, quality gate validation, and conventional commits. This provides a repeatable, auditable workflow that automates phase-by-phase execution according to your implementation guide.

Do I need a git repository and test suite to automate phase-by-phase execution?

Yes, automating phase-by-phase execution requires a git repository, a test suite, and a project structure aligned to your implementation guide. These elements provide the necessary foundation for orchestrating TDD cycles, quality checks, and structured commits.

Can I use phase-commit orchestration without integrating separate TDD and quality gate components?

No, phase-commit orchestration requires integration with separate dqx-tdd-cycle, dqx-quality-gate, and dqx-conventional-commit skills. It coordinates these individual components into a single workflow rather than replacing their underlying testing and validation functions.

Why does conventional commit fail after my test suite passes during phase execution?

Conventional commit execution fails after tests pass if quality gate criteria are not met. The orchestration enforces gating checks before allowing commits, ensuring quality standards are satisfied before moving forward and generating a progress report.

How does automated phase orchestration handle progress reporting and gating criteria?

Automated phase orchestration handles progress reporting by generating outputs after each coordinated step. It enforces gating criteria by ensuring quality gate checks pass before executing conventional commits, preventing phase progression until standards are met.