commit-code

Generate and push conventional git commits grouped by concern with issue references.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/kapilvirenahuja/garura --skill commit-code-kapilvirenahuja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-code
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/commit-code
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill commit-code-kapilvirenahuja

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you turn your current repository changes into clean, reviewable conventional commits that are grouped by concern, reference the correct existing issues, and safely push to the remote—without you manually crafting commit sets or dealing with mapping confidence issues.

Core Features & Use Cases

  • Concern-grouped commit creation: Analyzes staged, unstaged, and untracked changes and groups files so each commit contains only one coherent concern.
  • Conventional commit messages with issue references: Drafts commit messages that follow conventional commit format and include issue-number references, with approval required when issue mapping confidence is low.
  • Safe guardrails: Blocks committing sensitive files and halts when changes can’t be mapped to existing issues; exits gracefully when there are no changes.
  • Branch push and progress control: Pushes the branch to the remote (push failures are non-blocking) and supports pause/resume via a status file.

Quick Start

Use the commit-code play when you have uncommitted changes and want conventional, issue-linked commits grouped by concern.

Frequently Asked Questions about commit-code

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

FAQPage Schema
How do I group uncommitted git changes into conventional commits by concern?

The Skill analyzes staged, unstaged, and untracked files to group uncommitted git changes into conventional commits, ensuring each commit contains one coherent concern and references an existing issue before safely pushing to a non-default branch.

Can I link conventional commit messages to existing issues automatically?

Yes, conventional commit messages are automatically drafted with issue-number references. The Skill validates issue mapping confidence and pauses for human approval when confidence is low or changes cannot be mapped to existing issues.

What happens if I try to commit sensitive files to a protected git branch?

Safety guardrails block sensitive files from being committed and enforce branch guarding to prevent pushing to default branches. The Skill also halts if changes cannot be mapped to existing issues and exits gracefully when no changes are detected.

How do I push grouped git commits to a remote branch and resume if interrupted?

The Skill pushes grouped commits to the remote branch and supports pause and resume via a status file. Push failures are treated as non-blocking, allowing the workflow to continue while recording evidence artifacts based on configuration.

Does this approach require all code changes to map to an existing issue?

Yes, the workflow requires all code changes to map to an existing issue. If changes cannot be mapped, the process halts gracefully to prevent creating untraceable commits, ensuring every commit is issue-backed.