chsh-sk-ncs-git-commit

Extracts commit rationale from conversation and delegates git commits to a subagent.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-git-commit-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-ncs-git-commit
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-ncs-git-commit
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-git-commit-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing well-structured git commits with proper rationale, grouping, and style conventions is tedious and error-prone, especially when switching between Conventional Commits and Zephyr-style repositories. This Skill captures the reasoning already present in your conversation and hands off inspection, grouping, approval gates, and execution to a dedicated git subagent. ## Core Features & Use Cases - Rationale Extraction: Scans the conversation for stated goals, decisions, rejected alternatives, and ticket references to build commit subjects, bodies, and trailers. - Style Auto-Detection: Applies Conventional Commits for app/general repos and Zephyr style for NCS/Zephyr workspace repos automatically. - Doc-Sync Check: Warns when user-visible src/ changes lack corresponding PRD or dev-spec timestamp bumps before committing. - Use Case: After fixing a Wi-Fi reconnection bug in an NCS firmware project, ask to commit and push; the Skill passes the root-cause context and NCSDK ticket reference to the subagent, which proposes a grouped commit plan for your approval. ## Quick Start Ask the assistant to commit and push the current changes using the git commit skill.

Frequently Asked Questions about chsh-sk-ncs-git-commit

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

FAQPage Schema
How do I commit changes with proper rationale in git?

Ask the assistant to commit your changes; the Skill scans the conversation for stated goals, decisions, and rejected alternatives, then delegates to the chsh-ag-git subagent which handles inspection, grouping, and approval gates before executing the commit.

How to write Conventional Commits vs Zephyr-style commit messages?

The Skill auto-detects the repository type and applies the correct format. Conventional Commits are used for app and general repos, while Zephyr style is applied to NCS and Zephyr workspace repositories, with no manual configuration needed.

Can I commit without using the subagent?

Yes, inline execution is supported as a fallback when you explicitly ask to skip the subagent, when already running inside a subagent, or when chsh-ag-git is unavailable. The inline workflow follows the canonical reference in the chsh-ag-git agent file.

Does the commit workflow check documentation sync before committing?

Yes, for user app repos the subagent classifies src/ changes by severity and warns if PRD.md or dev-specs timestamps are not bumped in the same batch. This check is skipped for Zephyr-style repos or repos without those documentation paths.

What happens after pushing firmware commits?

The subagent does not watch CI or flash firmware. For CI monitoring and releases use the git-release skill, and for flashing pre-built artifacts with UART verification use the dev-debug skill in Mode G.