odin-git

Plugin odin-git from marketplace odin-marketplace in OutlineDriven/odin-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (40)

• agent-transcript

  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.

• atomic-issues-prs

  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.

• can-i-help

  Use when the user asks "where to help", "contribution opportunities", or "find a good first issue". Returns data-backed first steps. Not for PR review queues: use gh-review-requests.

• close-done

  Use when the user wants to batch-close resolved or outdated tracker items. The agent never closes tracker items itself. Not for individual closure or items still under active work.

• commit-push-current

  Use when a human explicitly asks to commit and push to the checked-out branch, including directly to the default branch, with no branch creation and no pull request. Not for a feature branch off the default: use commit-push-pr in its no-PR mode.

• commit-push-pr

  Use when asked to commit and push a feature branch, with or without a pull request. Its no-PR mode publishes without a PR. Not for a PR body alone: use create-pull-request.

• commit

  Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push-pr.

• create-branch

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

• create-pull-request

  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.

• finish-branch-menu

  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.

• fix-p0-issues

  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.

• gate-and-merge

  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.

• gh-review-requests

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

• git-branchless

  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.

• git-cleanup

  Use when the user explicitly invokes branch or worktree cleanup for a repo with accumulated local branches. Don''t use for remote branch deletion or force-push operations.

• git-guardrails

  Use when a repository needs Git safety controls: guard destructive commands, set up gitignore or fix gitignore when untracked files keep appearing, or install or repair a repository-local pre-commit hook from project gates, including package-manager-native commit-time checks. Not for remote, credent

• git-history-analysis

  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.

• git-workflow-and-versioning

  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.

• github-backlog-triage

  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.

• github-bug-report-triage

  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.

• github-issue-dedupe

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

• interactive-drop-selector

  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.

• issue-intake

  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.

• issue-now

  Use when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. Don''t use for bulk issue reconciliation or multi-issue sweeps.

• issue-triage

  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.

• land-contribution

  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.

• make-pr-easy-to-review

  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.

• new-branch-and-pr

  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.

• post-daily-new-issues

  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.

• post-merge-cleanup

  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.

• propose-issue

  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.

• publish-branch

  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.

• repo-health-triage

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

• resolve-merge-conflicts

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

• resolve

  Use when addressing review feedback in analyze or reception mode, or handling GitHub PR feedback in autonomous, interactive, or summary mode for a named PR target. Classifies, applies, replies, or summarizes comments.

• review-and-ship

  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.

• setup-repo-skills

  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.

• watch-and-repair-pr

  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.

• wontfix

  Use when the user wants to elicit refused directions, generalize them, and close matching tracker items as not planned. Not for duplicates, spam, or items closed as completed or obsolete.

• worktree

  Use when work needs an isolated git worktree: new work, an existing ref, a gated feature workspace, a manifest-tracked loop run, or a candidate patch captured without touching the current checkout (`capture-isolated-patch`). Not for plain branches: use create-branch. Not for remote, credential, publ

Similar plugins