Odin Git

Use when filing an approved task spec as a GitHub issue with a local archive and optional worktree implementer. Don't use for spec drafting without human interrogation and redaction gates.

Use when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.

Use when the user asks to create a new branch or start work on one. Not for remote, credential, publish, deploy, or irreversible changes.

Use when the user asks to fix P0s, address critical issues, or work on priorities from the weekly product briefing. Don't use for non-P0 issues or local bug fixes.

Use when the user asks to propose an issue, file or open a bug report, or turn a reported defect into a tracked issue. Not for fixing the defect, triaging existing issues, or reviewing PRs.

Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.

Use when landing a queue of open PRs: gate each PR, sweep its review feedback to root cause, then merge, repair, hold, or close it. Human-only.

Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.

Use when a repository needs a guard against force-push, forced reset, clean, branch deletion, working-tree discard, stash drop, reflog expire, or gc prune. Not for remote or irreversible changes.

Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.

Use when a human directly requests review and publication of an existing diff or delegated work. Not for merging pull requests, force pushes, history rewrites, or deployment.

Use when the user says set up gitignore, fix gitignore, or untracked files keep appearing. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body, with human approval and preview. Not for automated or model-initiated insertion.

Use when a human explicitly asks to commit and push directly to the default branch, with no feature branch and no pull request. Not for another checked-out branch: use commit-push-current.

Use when installing or repairing a repo-local pre-commit hook from the project gates, or when a repo needs package-manager-native commit-time checks. Not for remote or irreversible changes.

Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.

Use when a maintainer or collaborator explicitly asks to review and land one external pull request. Don't use for internal pull requests or landing without preserving contributor authorship.

Use when a human explicitly asks to ship work through a clean branch and pull request. Don't use for force-pushing, reusing conflicting branches, or widening the change scope.

Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.

Use when implementation is complete, the test suite is green, and an integration decision is needed for a development branch or worktree. Not for failing tests or starting new work.

Use when the user asks to find PRs to review or check the team review queue. Not for summarizing PR feedback: use resolve-pr-feedback. Read-only.

Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.

Use when a scheduled or watcher tick requests a repository-health pass. Not for source, label, merge, or close mutation.

Use when a human explicitly asks to commit and push to the checked-out branch, with no branch creation and no pull request. Not for the default branch by name: use commit-push-main.

Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.

Use when finding duplicate GitHub issues or checking for similar issues against a target issue. Not for closing, labeling, or modifying any duplicate issue.

Use when handling GitHub PR review feedback: autonomous fix-and-resolve, interactive per-comment walkthrough, or read-only severity summary. Not for non-GitHub feedback: use resolve.

Use when a human explicitly invokes a watcher cycle for an open pull request that must be watched until mergeable or blocked. Not for merge, force-push, or work outside the invoked cycle.

Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.

Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.

Use when a human explicitly requests the daily on-call issue digest from a named issue tracker for a configured Slack channel. Not for posting without explicit human authorization for that run.

Use when a candidate change must be produced without touching the working tree. Not for remote, credential, publish, deploy, or irreversible changes.

Use when a human explicitly asks to reshape or annotate one pull request for review. Don't use for pushing the rewritten branch or mutating any remote.

Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts. Not for people-mediation conflicts: use culture-conflict-mediation.

Use when evaluating whether a bug issue has sufficient detail and identifying missing reporter information. Not for non-bug issues or backlog triage: use github-backlog-triage.

Use when the user explicitly asks to choose which issues or pull requests to close interactively. Don't use for closing items without per-item selection and explicit approval.

Use when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don't use for single commits or for publishing to a package registry.