Skip to content

Commit 59931e6

Browse files
drbenvincentcursoragentCopilot
authored
Update issue-to-pr skill (#732)
* Update issue-to-pr skill. Clarify the command pointer to the specific issue-to-pr reference doc and require branch preflight from main before implementation to avoid stacking PR work on unrelated feature branches. Co-authored-by: Cursor <cursoragent@cursor.com> * Rename issue2pr command to issue-to-pr. Replace the Cursor command file name and text reference so all issue-to-PR command instances consistently use issue-to-pr naming. Co-authored-by: Cursor <cursoragent@cursor.com> * Update .cursor/commands/issue-to-pr.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * Use consistent <issue_number> placeholder in issue-to-pr workflow Replace <number> with <issue_number> in branch name examples to match the placeholder used in the rest of the workflow (Copilot suggestion). Made-with: Cursor --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent f36e9db commit 59931e6

3 files changed

Lines changed: 13 additions & 8 deletions

File tree

.cursor/commands/issue-to-pr.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
# Issue to Pull Request
2+
3+
This command points to the `pr-workflows` Skill in
4+
`.github/skills/pr-workflows/`. Specifically, see `.github/skills/pr-workflows/reference/issue-to-pr.md`.

.cursor/commands/issue2pr.md

Lines changed: 0 additions & 4 deletions
This file was deleted.

.github/skills/pr-workflows/reference/issue-to-pr.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,12 @@ description: Transform a GitHub issue into a complete pull request through a str
55

66
# Issue → PR Workflow
77

8+
## Branch preflight (required before any code edits)
9+
1. Check current branch and working tree state.
10+
2. Switch to `main` and update it from remote.
11+
3. Create the issue branch from `main`: `git checkout -b issue-<issue_number>-<short-description>`
12+
4. Only start implementation after confirming the new branch is based on `main`.
13+
814
## Discovery
915
1. Fetch issue details:
1016
```bash
@@ -14,9 +20,8 @@ description: Transform a GitHub issue into a complete pull request through a str
1420
3. Estimate complexity and share approach before implementation.
1521

1622
## Implementation
17-
1. Create a branch: `git checkout -b issue-<number>-<short-description>`
18-
2. Implement the fix, following `AGENTS.md` policies.
19-
3. Run pre-commit and tests until green (see `pre-commit.md`).
23+
1. Implement the fix, following `AGENTS.md` policies.
24+
2. Run pre-commit and tests until green (see `pre-commit.md`).
2025

2126
## Prepare PR
2227
1. Create `.github/pr_summaries/<issue_number> - <short-description>.md` with:
@@ -30,6 +35,6 @@ description: Transform a GitHub issue into a complete pull request through a str
3035

3136
## Create PR
3237
```bash
33-
git push -u origin issue-<number>-<short-description>
38+
git push -u origin issue-<issue_number>-<short-description>
3439
gh pr create --title "<PR title>" --body-file .github/pr_summaries/<issue_number> - <short-description>.md --base main
3540
```

0 commit comments

Comments
 (0)