skills.rest
soli92
soli92COMMUNITY
Explore all skills by this author →
GitHub

vcs-handoff

Coordinates per-task Git commits in a monorepo with mandatory human approval gates.

Updated Apr 30, 2026
Search Tags:#git#code review#version control#commit#monorepo#human approval#dev-agent
One-click install
npx skills add https://github.com/soli92/soli-projects --skill vcs-handoff-soli92
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vcs-handoff
Source: https://github.com/soli92/soli-projects/tree/main/.cursor/skills/vcs-handoff
Command: npx skills add https://github.com/soli92/soli-projects --skill vcs-handoff-soli92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It ensures that code produced by dev-agents is committed to version control in a controlled, traceable way, preventing unreviewed commits, accidental pushes, and out-of-scope changes from entering the repository. ## Core Features & Use Cases - Scoped per-task commits: Stages only the files belonging to the current task (TSK) and proposes a conventional commit message with task reference, never bundling multiple tasks into one commit. - Mandatory human gate: Shows the staged diff and proposed message and waits for explicit user approval before every commit; never pushes automatically. - VCS safety constraints: Blocks commits on detached HEAD, open conflicts, or out-of-scope staged changes, and forbids force pushes, amends, and branch switching. - Use Case: After a dev-agent finishes a backend task in the soli-projects monorepo, invoke this Skill to stage only that task's files, propose a feat(be): ... commit message, log the commit hash to wiki/log.md, and wait for your OK before committing on main. ## Quick Start Ask the agent to run the vcs-handoff procedure to stage and commit the current task's changes with a proposed commit message for your approval.

Frequently Asked Questions about vcs-handoff

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

FAQPage Schema
How do I commit agent-generated code one task at a time in Git?▼

Stage only the files belonging to the current task with git add <files>, then create one commit per task using a conventional message like feat(<layer>): <task title> with the task reference in the body. Never bundle multiple tasks into a single commit.

How to add a human approval step before AI agents commit code?▼

Require the agent to display the staged diff and proposed commit message, then wait for explicit user confirmation before running git commit. This gate applies to every commit, and pushes are never performed automatically.

Can an AI agent push commits or switch branches automatically?▼

No. The workflow forbids git push without explicit user confirmation and prohibits branch switching, force pushes, --no-verify, and --amend. The user decides which branch is checked out before invoking the dev-agent.

What happens if Git HEAD is detached before committing?▼

The procedure stops immediately and reports the issue. The user must check out a proper branch before any commit can proceed, since commits are only made on the main branch in this single-committer setup.

Why should I avoid git add . when committing task-scoped changes?▼

Using git add . stages unrelated modifications outside the task's scope, mixing concerns in one commit. Stage only the files touched by the current task, and stop if out-of-scope changes are already in the staging area.

Related Skills

Explore More Software Engineering Skills→
tincoppertincopper
10

trellis-finish-work

Archive completed Trellis tasks and write a session journal.

Community
Intermediate
dudqks0319-cpududqks0319-cpu

git_pushing

Automates Git commits and pushes with user approval and conventional commit messages.

Community
Basic
DataDogDataDog
648

lint

Run Hatch-based lint, format, and quality checks on modified files.

Official
Advanced
d3mingd3ming

commit-push-pr

Commit changes, push a branch, and open a pull request via GitHub CLI.

Community
Intermediate