git-integration

Standardize per-task commits in colocated Git workspaces using jj.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill git-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-integration
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/git-integration
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill git-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes per-task commits in colocated Git workflows, enabling precise traceability and safer rollbacks for AI-driven projects.

Core Features & Use Cases

  • Deterministic per-task commits to create a clean, bisectable history.
  • Commit message templates and phase-aware guidance for initialization, task completion, plan finalization, and handoff.
  • Clear examples and anti-pattern guidance to improve collaboration and governance.

Quick Start

Execute a per-task commit workflow for a new feature using jj in the colocated Git workspace.

Frequently Asked Questions about git-integration

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

FAQPage Schema
How do I standardize per-task Git commits for AI-driven workflows?

Standardize per-task Git commits by applying deterministic commit formats and atomic changes across initialization, task completion, and handoff phases. This creates a clean, bisectable history with precise traceability and safer rollbacks for AI-driven projects.

What is the best way to use jj for version control in colocated Git workspaces?

Using jj in colocated Git workspaces enables per-task commit workflows with deterministic message templates. It enforces atomic changes and clear task-level history, ensuring reproducible development history across AI-driven project phases.

How do commit message templates improve task-level history in version control?

Commit message templates improve task-level history by enforcing deterministic formats for initialization, plan finalization, and handoff rounds. They provide phase-aware guidance, eliminate ambiguous logs, and ensure reproducible development history for AI workflows.

Does this per-task commit workflow support manual Git operations alongside jj?

This per-task commit workflow operates in a colocated Git workspace using jj, enforcing deterministic commit formats and atomic changes. It cross-references with the commit protocol skill to ensure reproducible development history across all phases.

What anti-patterns should I avoid when managing AI workflow commits?

Avoid anti-patterns that break deterministic per-task commits, such as non-atomic changes or ambiguous commit messages. The workflow provides clear examples and anti-pattern guidance to maintain precise traceability, safer rollbacks, and clean bisectable history.