Open a pull request for the current feature branch
npx skills add https://github.com/kaelen2026/ai-harness-template --skill open-prانسخ والصق هذا الأمر في Claude Code لتثبيت المهارة
Commit a verified task implementation to git
Implement the current in-progress task
Convert a PRD into a technical specification
Recover from a failed or blocked task
Deploy the current release to a target environment
Roll back a deployment to the previous stable version
| name | open-pr |
| description | Open a pull request for the current feature branch |
$ARGUMENTS for the feature name. If empty, infer from current branch name (feat/<feature>).task-state/<feature>/ and confirm task statesgit log main..HEAD --oneline to get all commits on this branchdocs/modules/<feature>/TASKS.<feature>.md.github/pull_request_template.mdcommitted → list the unfinished tasks, abort: "The following tasks are not yet committed. Complete all tasks before opening a PR."main or master → abort: "Run this command from a feature branch."main → abort: "No changes to merge."git push -u origin feat/<feature>
If the remote branch already exists, use git push (not force-push). If it fails, ask the user to handle it manually.
Format: feat(<feature>): <one-sentence summary of the PR>
Fill in all sections from pull_request_template.md:
Summary (≤ 3 bullets — describe what changed, not how):
Related Issues:
Refs: #N or Fixes: #N from commit messagesN/AChanges (one line per major file or module):
Test Plan (checkable list):
Checklist:
gh pr create \
--title "<title>" \
--body "<body>" \
--base main \
--head feat/<feature>
✅ PR created: <PR URL>
Title: <title>
Base: main ← feat/<feature>
Tasks: N committed
Next steps:
- Wait for CI to pass
- Wait for code review
- After merge, run /release staging
| Situation | Action |
|---|---|
gh is not authenticated | Ask the user to run gh auth login, then abort |
| Push rejected by branch protection rules | Print the error, ask the user to check repository permissions |
| PR already exists for this branch | Print the existing PR URL, ask whether to update the PR description instead |
| Cannot reach GitHub | Print the PR title and body in the conversation for the user to create manually |