dotfiles

Use when handling any Git-backed change and safe task completion. Use when asked to implement a change in a repository and commit clean checkpoints; review a branch or repository for bugs, including review-only work; create commits or checkpoints; push and verify a remote branch; reconcile with an exact lease; integrate or discard a branch; classify or clean up a worktree; or close out Git work. If a repository task says "In Codex" or "In Claude Code," apply in either harness, even when mutation or publication is forbidden. Do not use for Git explanations or pasted summaries without repository action. Owns safe task-only commits, publication, completion choices, and provenance-aware cleanup without publishing non-task work.

Use when leading work from Cursor, Claude Code, or Codex that may need delegation across Cursor, Claude Code, Codex, Spark, browser/computer-use agents, or separate worktrees; deciding what stays local versus handed off; or coordinating multi-agent work.

Use when the user explicitly asks to get a GitHub branch or pull request merged, shipped, over the line, or closed out end to end: "get this merged", "drive it to merge", "ship this PR", "merge and close out this branch", or resume a previously stated merge/closeout workflow. Do not use for single-step PR operations, PR-description-only, review-only, status-only, issue-triage, check-only, CI-check-only, comment-only, ready-only, open-PR-only, draft-PR-only, or publish-only requests unless the user also states a merge or closeout goal. Requests to inspect checks, blockers, readiness, comments, or policy without asking to continue toward merge do not trigger this skill. Requests that say to open a PR, leave it draft, or that the PR is not ready to merge do not trigger this skill.

Use when the operator asks to get a branch, change set, draft PR, or pull request ready for review end to end: "get this PR review-ready", "make this ready for review", "prepare this draft PR for review", "mark ready for review", "tighten then publish for review", or "review-ready yeet". Do not use for review-only, status-only, PR-description-only, draft-PR-only, publish-only, merge, ship, or closeout requests unless the operator also states a ready-for-review outcome.

Use when working with Graphite `gt` stacks: creating or tracking stacked branches, navigating or reparenting a stack, restacking, submitting or updating stacked PRs, fixing Graphite metadata, or diagnosing stack ancestry and publication state.

Use when PR review loops, bot review reruns, CodeRabbit or Greptile cycles, unresolved pull request comments, ready-for-review, mark ready, merge readiness, blocked merges, stale review threads, requested reviewers, branch closeout, merge tasks, docs-only PRs, or skill-only PRs affect a pull request.

Use when creating or changing a GitHub PR, including drafts, title/body or draft/ready-state edits, `gh pr create/edit/ready`, Graphite submission, fork-sync or fixup PRs, and requests to yeet, ship, publish, or prepare a PR. Do not use for read-only inspection, comments, checks, threads, or merge-only work with unchanged PR text and state.

Use when returning to an existing open PR that already has review comments or threads and needs merge-focused refresh, conflict or CI repair, review-comment triage, scope trimming, or draft replies. Also use when given a PR number and/or branch for a stale, bloated, neglected, or long-running reviewed PR.

Use when changes appear ready to commit, merge, deploy, ship, release, finalize, or when the operator requests a review cycle, Ralph review, Ralph-review, ralph-review, review until clean, repeat until clean, clean review, or review and revise until clean.

Use when creating a stacked PR-fixup, follow-up patch PR, companion review-fix PR, or branch named with suffixes like -p0/-p1 that targets another open PR branch.

Use when syncing a fork with upstream, clicking Sync fork, using gh repo sync, merging upstream changes, or handling protected-main fork updates where upstream commit identity or intentional fork behavior must be preserved.

Use with using-git-worktrees when starting feature work that needs isolation from the current workspace, before executing implementation plans in a git worktree, choosing, auditing, moving, repairing, cleaning up, or handing off persistent worktrees, or resolving the local failure mode where coding agents use `.worktrees`, `worktrees`, `/tmp`, or global worktree paths instead of sibling `.wt` setup.

Use when creating or changing a GitHub PR title/body, including draft, stacked or Graphite, publish/ship/yeet, summary, media, diagram/atlas, access-note, caveat, or preservation-sensitive work. Do not use for read-only inspection, comments, checks, threads, or merge-only work with unchanged text.

Use when current public documentation is needed for a library, framework, SDK, API, CLI tool, or cloud service

Use when Serena setup, initialization, repair, or use is needed in a repository or worktree

Use when Ralph review semantics apply or reviewing-before-finalizing routes work to Ralph review: ralph-review, Ralph review, Ralph-review, review until clean, repeat until clean, clean review, or review and revise until clean for code, plans, specs, docs, branches, releases, PR readiness, or other artifacts.

Use when reviewing, re-reviewing, approving, requesting changes on, or drafting/posting comments for another person's open PR, including author updates or prior thread checks.

Use when performing comprehensive code reviews of a current diff, pre-closeout reviews, ready-for-review checks, pre-merge reviews, final review of non-trivial changes, scoped reviews of agent-facing docs or durable process instructions, reviewability passes, cleanup before review, tightening PRs, making changes easier to review, reducing reader burden, bloat, overengineering, dead code, WET code, code smells, React/Next bloat, missed reuse, duplicated generic behavior, excessive abstraction, or architecture tightening in a scoped change set.

Use when writing or reviewing `.sh`, `.bash`, or `.zsh` files, Makefile shell snippets, CI shell commands, or choosing between Zsh, Bash, and POSIX `sh` in this repo.

Use when preparing an agent, subagent, Task invocation, or agent definition after delegation has been chosen, including task-only prompts with no explicit role, model, or agent-type wording.

Use when a workflow reaches sudo, password-gated, privileged, or user-owned host mutation, including deploy, install, publish, pacman, systemctl, mount, failed sudo, no-new-privileges, require_escalated, AFK, non-interactive, or faillock-risk situations.

Use when using, creating, editing, testing, benchmarking, optimizing, or packaging skills with `skill-creator` outside Claude Code, or when `skill-creator` mentions Claude, claude-with-access-to-the-skill, `claude -p`, Claude.ai, Cowork, subagents, browser/viewer, trigger evals, description optimization, or packaging in a different agent harness.

Use when triaging, bulk triaging, auditing, or preparing GitHub Issues for nisavid/agent-armory, especially requests mentioning Agent Armory, Issue Tracker Ops, Efficient Coherence, triage depth, label axes, audit-labels, or Armory issue readiness.

Use when preparing a fork for agent-maintained upstream syncs, especially before the first broad sync or when no repo-local fork policy, divergence inventory, or sync gates exist.

Use when a task depends on who decides, approves, validates, acts, or closes out; when human, agent, operator, reviewer, or code-owner responsibility is ambiguous for merge, deploy, publish, release, install, delete, or handoff.

Use when a CLI reports quota, auth, cache, DNS, network, read-only filesystem, or missing-state failures inside Codex or another sandbox

Use when reviewing, refactoring, rewriting, or streamlining AGENTS.md, repo-local agent skills, skill references, or agent policy docs

Use when refreshing, refocusing, streamlining, polishing, or reorganizing README files, user guides, package docs, docs indexes, or other human-facing project documentation

Use when reviewing, renaming, editing, overriding, extending, or cleaning up installed skills that may be managed by plugins, lockfiles, upstream repos, generated skill managers, byte-identical local copies, or local extension policies.

Use when installing packages with pacman or paru for build, test, debug, packaging, or other transient work, especially when those packages should not remain explicitly installed after the task.