git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
Install / Use
npx skills add a5c-ai/babysitter --skill git-integrationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of git-integration
git-integration scores 92/100 on our quality scale, 874th of 2,790 Automation skills we index (top 32%).
Its SKILL.md is 7.9 KB long, well organised into 23 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.
With 1,809 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so git-integration is actively maintained.
- Our last check on 2026-10-27 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
git-integration compared with similar skills
All 4 of these similar skills score higher than git-integration; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| git-integration (this skill)by a5c-ai | 92 | 1.8k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install git-integration?
- Run
npx skills add a5c-ai/babysitter --skill git-integration. The install tabs above show the steps for each supported agent. - Which AI agents does git-integration work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is git-integration safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is git-integration still maintained?
- The repository was last updated about 2 months ago, so git-integration is actively maintained.
Skill content
View source on GitHubname: git-integration description: Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations. allowed-tools: Bash(*) Read Glob metadata: author: babysitter-sdk version: "1.0.0" category: gsd-core backlog-id: SK-GSD-008 graph: domains: [domain:software-engineering] skillAreas: [skill-area:agentic-loops, skill-area:orchestration-loop] workflows: [workflow:feature-development] topics: [topic:developer-experience] roles: [role:tech-lead, role:backend-engineer]
- Atomic commits: Each task produces exactly one commit containing all changes for that task.
- Separation of concerns: Planning file changes (
.planning/) are committed separately from code changes.
This corresponds to the patterns in the original references/git-integration.md and references/git-planning-commit.md.
Capabilities
1. Atomic Commit Per Task
Each task in a plan produces one atomic commit:
# After completing task 1 of PLAN-1.md
git add src/auth/oauth.ts src/auth/types.ts
git commit -m "feat(auth): implement OAuth2 login endpoint
Phase 72, Plan 1, Task 1: Implement login endpoint
- Added POST /api/auth/login with email/password validation
- Returns JWT token on success, 401 on invalid credentials
- Rate limited to 5 attempts per minute
Refs: Phase-72/PLAN-1/Task-1"
Commit message format:
<type>(<scope>): <short description>
Phase <N>, Plan <M>, Task <K>: <task title>
- <change 1>
- <change 2>
Refs: Phase-<N>/PLAN-<M>/Task-<K>
Types: feat, fix, refactor, test, docs, chore, style, perf.
2. Planning File Commits
Planning files are committed separately from code:
# After generating plans
git add .planning/phase-72/PLAN-1.md .planning/phase-72/PLAN-2.md
git commit -m "plan(phase-72): create execution plans
Phase 72: Authentication
- PLAN-1.md: OAuth2 login and token management (4 tasks, wave 1)
- PLAN-2.md: Auth middleware and role guards (3 tasks, wave 1)
Refs: Phase-72/planning"
Planning commit types: plan, state, research, context, verify, audit.
3. Commit Message Generation
Generate commit messages from task context:
Input:
phase: 72
plan: 1
task: 1
title: "Implement login endpoint"
type: "feat"
scope: "auth"
changes: ["POST /api/auth/login endpoint", "JWT token generation", "Rate limiting"]
Output:
"feat(auth): implement OAuth2 login endpoint
Phase 72, Plan 1, Task 1: Implement login endpoint
- Added POST /api/auth/login endpoint
- JWT token generation on success
- Rate limiting (5 attempts/minute)
Refs: Phase-72/PLAN-1/Task-1"
4. Git Tag Creation
Create annotated tags for milestone completions:
git tag -a v1.0 -m "Milestone v1.0: MVP Launch
Phases completed: 70, 71, 72, 73
Requirements covered: R1-R11
Audit result: PASSED
Key deliverables:
- Project scaffolding and CI pipeline
- Database layer with migrations
- OAuth2 authentication
- REST API endpoints"
5. Branch Status Detection
Detect current branch state:
{
"branch": "main",
"clean": false,
"staged": ["src/auth/oauth.ts"],
"unstaged": [".planning/STATE.md"],
"untracked": ["src/auth/oauth.test.ts"],
"ahead": 3,
"behind": 0
}
6. Planning-Aware File Staging
Separate .planning/ files from source code files:
# Stage code changes only
git add src/auth/oauth.ts src/auth/types.ts
# Stage planning changes only (separate commit)
git add .planning/phase-72/SUMMARY.md .planning/STATE.md
Rules:
- Code changes: committed with task-level commit messages
- Planning changes: committed with phase-level commit messages
- Mixed commits: never (always separate planning from code)
7. Commit History Analysis
Analyze commit history for progress tracking:
Phase 72 commits:
abc1234 feat(auth): implement OAuth2 login endpoint (Task 1)
def5678 feat(auth): add token refresh mechanism (Task 2)
ghi9012 feat(auth): implement logout and revocation (Task 3)
jkl3456 test(auth): add auth endpoint tests (Task 4)
Total: 4 commits, 12 files changed, +450 -30 lines
8. Diff Summary Generation
Generate diff summaries for SUMMARY.md:
Changes summary:
Files created: 4
Files modified: 2
Files deleted: 0
Lines added: 450
Lines removed: 30
New files:
src/auth/oauth.ts (120 lines)
src/auth/tokens.ts (85 lines)
src/auth/types.ts (45 lines)
src/middleware/auth.ts (90 lines)
Modified files:
src/routes/index.ts (+15 -2)
package.json (+3 -0)
Tool Use Instructions
Creating an Atomic Commit
- Use
Bashto rungit statusto see current changes - Use
Bashto stage only the files related to the current task:git add <files> - Generate commit message from task context
- Use
Bashto commit:git commit -m "<message>" - Verify commit succeeded with
git log -1
Creating a Planning Commit
- Use
Bashto identify planning file changes:git status .planning/ - Stage only planning files:
git add .planning/<files> - Generate planning commit message
- Commit with planning-specific type prefix
Creating a Milestone Tag
- Use
Readto load milestone audit data for tag annotation - Use
Bashto create annotated tag:git tag -a <version> -m "<annotation>" - Verify tag with
git tag -l <version>
Checking Branch Status
- Use
Bashto rungit status --porcelain - Use
Bashto rungit rev-list --count HEAD..@{upstream}for behind count - Use
Bashto rungit rev-list --count @{upstream}..HEADfor ahead count - Return structured status
Process Integration
execute-phase.js- Atomic commit per task during executionverify-work.js- Commit verification results and fixesquick.js- Atomic commit for quick task executiondebug.js- Commit debug fixescomplete-milestone.js- Create milestone git tagadd-tests.js- Commit each test file atomicallyresearch-phase.js- Commit research documentplan-phase.js- Commit generated plans (planning commit)
Output Format
{
"operation": "commit|tag|status|history|diff",
"status": "success|error",
"commit": {
"hash": "abc1234",
"message": "feat(auth): implement OAuth2 login endpoint",
"filesChanged": 3,
"linesAdded": 120,
"linesRemoved": 5
},
"tag": {
"name": "v1.0",
"annotation": "Milestone v1.0: MVP Launch"
},
"branchStatus": {
"branch": "main",
"clean": true,
"ahead": 0,
"behind": 0
}
}
Configuration
| Setting | Default | Description |
|---------|---------|-------------|
| autoCommit | true | Automatically commit after each task |
| commitMessageFormat | conventional | Commit message format (conventional/simple) |
| separatePlanningCommits | true | Separate planning from code commits |
| signCommits | false | GPG-sign commits |
| tagPrefix | v | Prefix for milestone tags |
Error Handling
| Error | Cause | Resolution |
|-------|-------|------------|
| Nothing to commit | No changes to stage | Verify task made expected changes |
| Merge conflict | Conflicting changes in working tree | Resolve conflicts before committing |
| Dirty working tree | Uncommitted changes from previous task | Commit or stash before proceeding |
| Tag already exists | Milestone tag already created | Use --force or choose different tag name |
| Detached HEAD | Not on a branch | Checkout a branch before committing |
Constraints
- Never create commits with mixed planning and code changes
- Each task gets exactly one code commit (atomic)
- Commit messages must follow the structured format with phase/plan/task references
- Planning commits use planning-specific type prefixes (plan, state, research, etc.)
- Tags are annotated (not lightweight) with milestone summary
- Never force-push or rewrite history on shared branches
- Always check for clean working tree before starting a new task
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
