gh-issue-kickoff
Kick Off Issue Work
Use this skill to start work on a GitHub issue from live GitHub data and current repo context. Treat readiness review as the opening gate inside the kickoff, not the end goal.
Overview
Assume the issue is probably good enough to start from. Only stop or escalate when you find a material blocker, contradiction, stale detail, or planning-critical omission that would make execution unsafe or incoherent.
Keep kickoff focused on the first executable plan. If the user wants a deep critique, tradeoff review, or pressure test of an existing issue, PR, or branch plan, use gh-plan-review instead of widening this skill into a broader review pass.
Boundary Rules
- Use this skill to start from a GitHub issue and turn it into the first execution-ready plan.
- Use
gh-plan-reviewwhen the user wants a deeper review of an existing implementation plan, branch approach, or test strategy before coding. - Do not silently widen kickoff into a report-only plan audit. Keep the work centered on issue readiness, safe issue hygiene, and the first actionable plan.
Core Workflow
- Fetch the authoritative issue state with
gh issue view {<number> | <url>} --json assignees,author,body,comments,labels,milestone,number,projectItems,state,title,updatedAt,url.
More from beeman/skills
gh-pr-review-comments
Address GitHub pull request review comments on an existing feature branch. Use when Codex needs to fetch live PR review comments with gh, classify each comment as actionable, optional, or rejectable, apply only accepted fixes on the same branch, run a self-review pass for contradictions introduced by those fixes, and then either create a new commit or follow an explicitly approved history-rewrite path before pushing, resolving threads, and re-requesting review.
8feature-structure
Use when reorganizing code around feature boundaries, splitting monolithic screen components or state hooks, deciding whether logic belongs in data-access, feature, ui, or child features, or moving orchestration out of prop-heavy UI files.
8gh-pr-create
Create a GitHub pull request from local repo changes. Use when Codex must get feature-branch setup and local commit packaging from `gh-commit`, get approval before pushing, show the exact PR title and body that will be sent, handle single-commit and multi-commit branch flows explicitly, and open or update the PR with gh.
7gh-plan-review
Review, challenge, pressure-test, or refine an implementation plan tied to a GitHub issue, GitHub PR, or active branch. Use when Codex needs to inspect the authoritative GitHub state and local repo context, run a scope challenge, identify material plan risks, surface real tradeoffs, and finish with a fixed review summary without mutating code or git state.
5gh-pr-rebase
Rebase an existing GitHub PR branch onto the repository default branch. Use when Codex needs to fetch the latest default-branch history, keep the local default branch current when that is safe, rebase the current feature branch, resolve straightforward conflicts carefully, ask the user to decide ambiguous conflicts, and update the remote PR branch with `git push --force-with-lease` after any required approval.
5gh-commit
Prepare a local Git commit from repo changes. Use when Codex needs to get onto the correct feature branch if needed, inspect `git status --short`, the current diff, and branch history, run the smallest relevant verification, add any required changeset, and package the tracked work into either a new commit or an explicitly approved amend flow before any push or PR step.
4