trw-commit

Generate TRW-compliant commit messages with contextual trailers and provenance data.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/wallter/trw-mcp --skill trw-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trw-commit
Source: https://github.com/wallter/trw-mcp/tree/main/src/trw_mcp/data/codex/skills/trw-commit
Command: npx skills add https://github.com/wallter/trw-mcp --skill trw-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convention-enforced git commits ensure consistent, auditable changes and strengthen sprint integration by automatically generating TRW-compliant commit messages with WHY rationale and PRD linkage.

Core Features & Use Cases

  • Enforces TRW commit conventions: analyzes changes and formats messages as type(scope): message with WHY and PRD trailers.
  • Context-aware trailers: attaches FR and PRD context from active PRD run when available.
  • Branch-naming and validation: checks branch naming and flags deviations for review before commit.
  • Use Case: when contributing to a TRW project, automatically generate a compliant commit that documents rationale and PRD linkage.

Quick Start

Run the TRW commit helper to create a compliant commit message and stage the changes.

Frequently Asked Questions about trw-commit

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

FAQPage Schema
How do I automate git commit message formatting for TRW conventions?

Automating TRW commit conventions involves analyzing staged changes and generating messages formatted as type(scope): message with WHY rationale and PRD linkage trailers, ensuring consistent, auditable commits for sprint integration.

What is a TRW commit convention and when do I need it?

A TRW commit convention is a structured message format that enforces documenting WHY rationale and PRD linkage alongside code changes, required when contributing to a TRW project to ensure consistent, auditable changes and sprint integration.

How do I attach PRD and FR context to my git commit trailers?

Attaching PRD and FR context to commit trailers is done by reading the active PRD run data and appending it to the commit payload as provenance data, providing sprint integration context directly within the commit history.

Can I validate git branch naming before staging a TRW commit?

Validating git branch naming before staging a TRW commit is supported by checking branch names against expected conventions and flagging deviations for review, preventing non-compliant branches from receiving structured commits.

What's the best way to enforce consistent commit messages across a development team?

Enforcing consistent commit messages is best achieved by automating the analysis of changes to generate structured payloads with type(scope) formatting and contextual trailers, eliminating manual formatting errors and strengthening sprint integration.