Issue To Pr

Turn a GitHub issue into a branch, fix, and PR.

Skill metadata

Source	Bundled (installed by default)
Path	skills/github/issue-to-pr
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	github, issues, pull-request, kanban, workflow
Related skills	github-issues, github-pr-workflow, git-local-workflow, plan

Reference: full SKILL.md

信息

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Issue to PR

End-to-end recipe: pick a GitHub issue → plan → implement → open a PR that closes the issue. Optionally track progress on a kanban card.

When to Use

• User asks to "fix issue #N" or "ship a PR for this bug"
• Kanban worker assigned an issue URL / number
• After /plan for a multi-file issue fix

Prerequisites

• gh authenticated (github-auth)
• Clean-enough git worktree; prefer a new branch
• Related skills: plan, git-local-workflow, github-pr-workflow

How to Run

1. Read the issue:

gh issue view <N> --json number,title,body,labels,url

2. Optional kanban track:

vibeos kanban create "Issue #<N>: <title>" --assignee default \
  --body "Source: <issue url>"

3. Plan (do not code yet on complex issues):

/plan Fix GitHub issue #<N>: <title>

Wait for approval if plan-before-act is on.

4. Branch + implement with file tools; commit via git-local-workflow.

5. Open PR linking the issue:

gh pr create --title "fix: <short title>" --body "$(cat <<'EOF'
## Summary
- Fixes #<N>

## Test plan
- [ ] …

EOF
)"

6. Comment on the issue/kanban with the PR URL; kanban_complete when CI is green (or note follow-ups).

Quick Reference

Step	Tool / command
Issue	gh issue view
Plan	/plan or plan skill
Commit	git-local-workflow
PR	github-pr-workflow / gh pr create
Track	kanban_* tools

Procedure

1. Restate acceptance criteria from the issue body.
2. Keep the change scoped to the issue — no drive-by refactors.
3. Put Fixes #<N> or Closes #<N> in the PR body.
4. If blocked, kanban_block with reason; do not silently stop.

Pitfalls

• Do not force-push shared branches.
• Do not commit secrets from the issue discussion.
• Large issues: split into linked PRs and say so in the plan.

Verification

• PR URL exists and references #<N>.
• CI started (or documented why not).
• Local tests / smoke from the plan were run.