# Documentation

- [Introduction](/docs/overview.md): What git-span is, what a span is, and why declared-but-unenforced coupling deserves a tool.
- [Getting started](/docs/getting-started.md): Install the git-span CLI, then wire it into Claude Code, OpenAI Codex, or OpenCode.
- [Agent integration](/docs/agent-integration.md): What the Claude Code, Codex, and OpenCode plugins wire up — workflow hooks, three skills, and the expert subagent.
- [Concepts](/docs/concepts.md): Precise definitions for spans, anchors, the why, drift, and the trust boundary around git-span's output.
- Guides
  - [Reconcile drifted spans](/docs/guides/reconcile-drifted-spans.md): Find drifted anchors with git span drift, auto-resolve what's mechanically safe, and manually re-anchor the rest.
  - [Re-anchor after an edit](/docs/guides/re-anchor-after-an-edit.md): Update a span's anchors after a deliberate code change — in place, or to a new range.
  - [Mine span candidates from history](/docs/guides/mine-span-candidates.md): Find real but unenforced couplings by mining git history for files that change together, then confirm and declare them.
- [Command reference](/docs/commands.md): Every git-span subcommand, grouped by task, with flags and exit behavior.
- [CI & git integration](/docs/ci.md): git span drift as the CI enforcement backstop, the local pre-commit hook, and the optional merge driver.
- [Reference](/docs/reference.md): Span name grammar, anchor syntax, the .span/ storage model, exit codes, and configuration.