sdd-commit

Generate conventional commit messages and PR templates for SDD workflows.

48|4|Updated Sep 8, 2025
One-click install
npx skills add https://github.com/yi-john-huang/sdd-mcp --skill sdd-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-commit
Source: https://github.com/yi-john-huang/sdd-mcp/tree/main/.claude/skills/sdd-commit
Command: npx skills add https://github.com/yi-john-huang/sdd-mcp --skill sdd-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear, consistent commit messages and PR documentation to improve traceability in SDD workflows.

Core Features & Use Cases

  • Enforces Conventional Commits format with type, scope, and subject.
  • Provides templates for PR descriptions and change documentation.
  • Helps teams maintain a clean, review-friendly history and changelog.

Quick Start

To start, stage your changes and run the tool to generate a conventional commit message and a PR template.

Frequently Asked Questions about sdd-commit

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

FAQPage Schema
How do I generate conventional commit messages for feature branches?

To generate conventional commit messages, stage your changes and run the tool to automatically create messages with type, scope, and subject for consistent local development history.

What is the best way to standardize pull request documentation for collaborative projects?

Standardizing pull request documentation is achieved by applying PR templates and atomic change documentation rules, ensuring collaborative projects maintain a clean, review-friendly history and changelog.

How do conventional commits improve traceability in SDD workflows?

Conventional commits improve traceability in SDD workflows by enforcing a structured format with type, scope, and subject, providing clear and consistent commit messages for better project history tracking.

Can I use this tool to automate PR template generation for local development?

Yes, you can automate PR template generation for local development by staging your changes and running the tool, which outputs structured PR descriptions and atomic change documentation.

Do I need to manually format commit types and scopes when using conventional commits?

No, you do not need to manually format commit types and scopes; the tool automatically enforces conventional commits rules, generating the correct structure for type, scope, and subject.