skills.rest
narrative-io
narrative-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

commit

Generate Conventional Commits with Shortcut ticket references.

Updated Jul 25, 2025
Search Tags:#git#workflow#commit#code-review#shortcut#conventional-commits
One-click install
npx skills add https://github.com/narrative-io/data-collaboration-mcp --skill commit-narrative-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/narrative-io/data-collaboration-mcp/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/narrative-io/data-collaboration-mcp --skill commit-narrative-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and standardize code-change histories by generating well-structured conventional commits that automatically link to Shortcut tickets, improving traceability and review efficiency.

Core Features & Use Cases

  • One-commit-per-change discipline: Breaks work into logically cohesive commits to tell a clear story.
  • Shortcut-linked messages: Each commit includes a Shortcut ticket reference for end-to-end traceability.
  • Conventional-Commits formatting: Enforces standard prefixes (feat, fix, chore, etc.) and proper structure for tooling compatibility.
  • Use case: When preparing a release, create separate commits for feature work, fixes, and documentation, each with an appropriate Shortcut reference.

Quick Start

Run through your changes and create a sequence of single-purpose commits, each with a descriptive message and a Shortcut ticket reference in Conventional Commits format.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I format conventional commits with Shortcut ticket references?▼

Conventional commits with Shortcut ticket references use standard prefixes like feat or fix, followed by a descriptive message and the Shortcut ticket ID to ensure end-to-end traceability across your code review workflow.

Why should I use one-commit-per-change discipline in git workflows?▼

One-commit-per-change discipline in git workflows breaks work into logically cohesive commits, creating a clear release history that simplifies code reviews and preparation by telling a distinct story for each modification.

What is the best way to link Shortcut tickets to git commits?▼

The best way to link Shortcut tickets to git commits is by enforcing Conventional Commits syntax that automatically includes the Shortcut ticket reference, ensuring traceable commit messages during pull request preparation.

Can I use conventional commit prefixes for release histories in software projects?▼

Yes, conventional commit prefixes like feat, fix, and chore format release histories in software projects requiring traceable commit messages, separating feature work, fixes, and documentation into distinct commits.

Does enforcing conventional commits syntax improve code review efficiency?▼

Enforcing conventional commits syntax improves code review efficiency by standardizing commit message structure, which allows reviewers and tooling to quickly parse changes linked to Shortcut tickets.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
arbazkhan971arbazkhan971
26

changelog

Generate structured changelogs and release notes from git commit and PR history.

Community
Advanced
ESO-ToolkitESO-Toolkit
2

workflow

Automates Git feature branches from Jira tickets through commit-to-PR lifecycle with quality checks.

Official
Advanced
TibsfoxTibsfox
69

git-commit

Generate Angular-format conventional commit messages from user prompts.

Community
Intermediate