create-pr

Files (1)

• SKILL.md

SKILL.md (first lines)

# create-pr

Ship the finished work as a pull request. The branch already exists (created in `develop` phase D). Keep the PR small and readable; the full detail lives in the tracker task.

## Steps

1. **Confirm the branch and diff.** `git status` + `git diff <base>...HEAD`. Never open a PR from the main branch.
2. **Commit** any pending work in atomic commits with clear messages (follow `.context/styling.md` if present). Never silence `git commit` output: a failing pre-commit hook aborts the commit and its error is the only signal. After each commit, check the exit code and that `git log -1 --oneline` shows it; if a hook reformatted files, re-stage and commit again before pushing.
3. **Push** the branch: `git push -u origin HEAD`.
4. **Open the PR** with the tracker's CLI — `gh pr create` for GitHub, `glab mr create` for GitLab (see `docs/agents/issue-tracker.md`):
   - **Title**: what the change does, imperative mood.
   - **Body**: what / why + a link to the tracker task. Keep it short — detail lives in the task. If that task has subtasks, link the subtask this change implements, never the parent; ask if it's ambiguous.
   - **Reviewers / labels / CI**: apply whatever your repo documents in `.context/`. This skill hardcodes none.
5. **Report** the PR URL.
6. **Remove the worktree the PR came from.** If the PR was opened from a linked worktree (not
   the main one), the branch now lives on origin; bring it back later if more work is needed.
   Leave the worktree and remove it in one command, so the shell never sits in a deleted directory:
   ```bash
   wt="$(git rev-parse --show-toplevel)"; main="$(git worktree list --porcelain | head -1 | cut -d' ' -f2-)"
   [ "$wt" != "$main" ] && cd "$main" && ~/.claude/skills/disk-cleanup/scripts/worktree-cleanup.sh --remove "$wt"
   ```
   It refuses, changing nothing, if there are uncommitted changes or the branch tip is not on
   origin — then report why and keep it. Large `node_modules` make this slow: run it in the background.

## Notes

- This is the **generic** delivery skill. Anything repo-specific — required reviewers, CI gates, a PR template, protected-branch rules, a branch-naming convention — belongs in your repo's `.context/`, not here.
- **Non-analysis branches only.** An `analysis` task produces a report, not a PR.

From pabloleonalcaide/development-skills, MIT.

More from pabloleonalcaide/development-skills