commit-spec

Aggregate phase summaries from ROADMAP.md into a conventional commit message.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill commit-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-spec
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/commit-spec
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill commit-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered phase summaries into a single, coherent commit message that accurately captures the entire spec's work and rationale.

Core Features & Use Cases

  • Phase aggregation: Reads completed phases from ROADMAP.md and collects per-phase SUMMARY.md to understand what changed.
  • Synthesis & formatting: Produces a comprehensive commit message in conventional format that tells the full story across phases.
  • Automation & commitment: Applies the resulting message as a git commit that records the complete evolution of the spec.
  • Use Case: When releasing a multi-phase feature, generate a single, well-structured commit describing all phases and changes.

Quick Start

Command the system to generate the full commit message and apply it to the repository for all completed phases.

Frequently Asked Questions about commit-spec

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

FAQPage Schema
How do I generate a conventional commit message for a multi-phase feature release?

To generate a conventional commit message for a multi-phase feature, this Skill reads completed phases from ROADMAP.md and aggregates their SUMMARY.md files to synthesize one coherent commit log. It then automatically applies this comprehensive message as a git commit.

How can I consolidate scattered git phase summaries into a single commit?

You can consolidate scattered git phase summaries by loading ROADMAP.md to identify completed phases, gathering per-phase SUMMARY.md files, and synthesizing them into a single conventional-commit formatted message that records the full evolution.

What is the best way to automate git commits for a spec-workflow?

The best way to automate git commits for a spec-workflow is to aggregate the per-phase SUMMARY.md outputs across all completed phases, synthesizing them into a comprehensive conventional-commit message before committing the changes.

Do I need ROADMAP.md and SUMMARY.md files to automate conventional commits?

Yes, you need ROADMAP.md and SUMMARY.md files to automate conventional commits, as the workflow strictly enforces loading the roadmap to identify phases and gathering summary files to synthesize the final commit message.

When should I avoid aggregating phase summaries into a single commit?

You should avoid aggregating phase summaries into a single commit if your software engineering workflow does not follow a multi-phase spec structure or lacks the required ROADMAP.md and SUMMARY.md files for synthesis.

Does commit-spec work with multi-phase software engineering workflows?

Yes, commit-spec works with multi-phase software engineering workflows by aggregating summaries from completed spec phases to compose a single, coherent conventional-commit formatted log for the entire feature.