commit

Automate branch creation, commits, PR review, and gated merge with human approval.

3|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/YanCheng-go/danskprep --skill commit-yancheng-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/YanCheng-go/danskprep/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/YanCheng-go/danskprep --skill commit-yancheng-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the complete software change workflow from branch creation to PR review and final merge, enforcing a mandatory human approval gate before integration.

Core Features & Use Cases

  • End-to-end ship cycle: branch → commit → PR → self-review → human approval → merge.
  • Governance and compliance: enforce branch naming, commit hygiene, PR existence, and documentation updates.
  • Collaboration enablement: supports teams practicing formal code reviews and gated merges to ensure quality and accountability.

Quick Start

Create a feature branch, commit changes with an imperative message, open a PR for review, and await human approval before merging.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate a git workflow with a mandatory human approval gate before merging?

To automate a git workflow with a mandatory human approval gate, this Skill orchestrates the complete cycle from branch creation and commit to PR review and final merge. It enforces branch naming, commit hygiene, and requires a human sign-off before integration.

How does a pull request workflow enforce commit hygiene and branch naming conventions?

A pull request workflow enforces commit hygiene and branch naming by applying governance rules before review. This Skill automates these checks to ensure collaborative development teams maintain quality, accountability, and formal code review standards.

What is the best way to manage code review and gated merges for collaborative development teams?

The best way to manage code review and gated merges is using an end-to-end ship cycle that includes self-review and human approval. This Skill automates that pipeline, enforcing documentation updates and PR existence before allowing final integration.

Can I use this automated branch creation and code review process for compliance governance?

Yes, you can use this automated branch creation and code review process for compliance governance. It enforces formal review workflows, commit standards, and a mandatory human approval gate to ensure accountability during software integration.

Do I need existing git branches to start the automated PR review and merge cycle?

No, you do not need existing git branches to start the automated PR review and merge cycle. The Skill initiates the workflow by creating a feature branch, then proceeds to commit changes and open a pull request for review.

Why does my code merge require a self-review and human sign-off before final integration?

Your code merge requires a self-review and human sign-off to enforce quality and accountability in collaborative development. This gated merge mechanism ensures all changes meet formal review standards before integrating into the main branch.