Menu
Use for commit, push, pull request, issue, and GitHub CLI workflows; emphasizes diff-grounded text and safe non-interactive commands.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Watch an open GitHub pull request for CI, mergeability, bot reviews, and human feedback until it is ready, closed, or blocked.
Harness-portable autonomous delivery loop for a scoped software task: front-load uncertainty, produce or confirm a plan, implement with TDD and validation, run review passes, prepare git/GitHub artifacts, and babysit the PR when authorized. Use when the user wants a mostly hands-off problem-to-PR workflow.
Harness-portable planning and requirements-capture workflow for turning vague, risky, architectural, multi-workstream, or scope-drift-prone requests into durable artifacts before implementation. Use when the user asks to scope, plan, workshop, write a spec, capture acceptance criteria, prepare an implementation handoff, or when product intent should not be guessed.
Read-only reviewer for checking whether an implementation milestone matches an approved plan or spec.
Guide agents to choose a review pass intentionally and keep findings structured.
Use when starting feature work that should be isolated from the main checkout; creates or verifies an isolated git worktree with safety checks.
| name | git-github-ops |
| description | Use for commit, push, pull request, issue, and GitHub CLI workflows; emphasizes diff-grounded text and safe non-interactive commands. |
Use this skill when the user asks for git or GitHub execution, not merely code edits.
gh for GitHub operations.git or gh.AGENTS.md for actions requiring explicit approval.Summarize only what is visible in the diff.
Example shape:
Add project-local agent workflow docs
- Add shared AGENTS guidance and Claude pointer
- Curate reusable local skills for worktrees, git ops, and reviews
- Ignore local plans and worktree scratch directories
Commit with file input:
git diff --staged
git commit -F /tmp/guest-pass-commit-message.txt
PR titles should name the touched area and outcome:
agents: add shared workflow guidance
PR bodies should be written to a temp file and passed with --body-file.
## Summary
- What changed
- Why it is needed
## Testing
- [x] Command or manual validation
## Risks
- Notable risks, migrations, or follow-up constraints
## Scope
- In scope: ...
- Out of scope: ...
Create only after approval:
gh pr create --title "<title>" --body-file /tmp/guest-pass-pr.md --base main --head <branch>
Use file-first patterns:
gh pr comment <number> --body-file /tmp/guest-pass-pr-comment.md
gh issue comment <number> --body-file /tmp/guest-pass-issue-comment.md
Do not add a literal Labels section to issue bodies; use GitHub labels.