II.
Page JSON
Structured · livepage:docs-harness-features-backlog-gaps-prompt-engineering-gap-prompt-012
GAP-PROMPT-012: Git Safety Protocol Prompt Section json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-harness-features-backlog-gaps-prompt-engineering-gap-prompt-012",
"_kind": "Page",
"_file": "wiki/docs/harness-features-backlog/gaps/prompt-engineering/gap-prompt-012.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/harness-features-backlog/gaps/prompt-engineering/GAP-PROMPT-012.md",
"sourceKind": "repo-docs",
"title": "GAP-PROMPT-012: Git Safety Protocol Prompt Section",
"displayName": "GAP-PROMPT-012: Git Safety Protocol Prompt Section",
"slug": "docs/harness-features-backlog/gaps/prompt-engineering/gap-prompt-012",
"articlePath": "wiki/docs/harness-features-backlog/gaps/prompt-engineering/GAP-PROMPT-012.md",
"article": "\n# GAP-PROMPT-012: Git Safety Protocol Prompt Section\n\n| Field | Value |\n|-------|-------|\n| Category | prompt-engineering |\n| Priority | Medium |\n| Effort | S |\n| Status | Missing |\n\n## Description\nInject git safety protocol rules into task prompts for effects that involve version control operations. Prevents delegated agents from destructive git operations, hook-skipping, force-pushing, amending published commits, and other git mishaps during orchestrated code tasks.\n\n## Current State\nCC includes detailed git safety rules in its system prompt (never update git config, never skip hooks, always create new commits instead of amending, prefer specific file staging over `git add -A`). When babysitter delegates to CC, these rules apply. When delegating to other harnesses, no git safety rules exist in the task prompt. Process definitions that involve code changes have no standardized git protocol.\n\n## Target State\nA `gitSafety` prompt section injected when task context indicates version control operations (code modification tasks, commit/push tasks, branch management). Content: never force-push to main, never skip hooks, create new commits not amends, stage specific files not everything, check for secrets before committing. Configurable per process definition (some processes may need to amend commits intentionally).\n\n## Dependencies\n- [GAP-PROMPT-001](../prompt-engineering/GAP-PROMPT-001.md) -- strata model for section placement\n- [GAP-PROMPT-010](../prompt-engineering/GAP-PROMPT-010.md) -- safety framework for blast radius reasoning\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| Prompts module | `packages/sdk/src/prompts/` |\n| CC prompt phrasing analysis | [`11-prompt-phrasing-analysis.md`](../../11-prompt-phrasing-analysis.md) -- Section 6 (Git Operations Protocol) has exact CC phrasing for commit protocol and safety rules |\n\n## Recommendation\nPhase 2-3 implementation. Small effort -- extract git safety protocol from CC analysis, add as conditional prompt section for code tasks.\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "page:docs-harness-features-backlog",
"to": "page:docs-harness-features-backlog-gaps-prompt-engineering-gap-prompt-012",
"kind": "contains_page"
}
]
}