Menu
Automates the process of creating a pull request using the custom issue_manager script, replacing the need for gh CLI.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | Pull Request Workflow |
| description | Automates the process of creating a pull request using the custom issue_manager script, replacing the need for gh CLI. |
This skill allows you to create GitHub Pull Requests using the local scripts/issue_manager.py script, which directly interacts with the GitHub API. This is useful when the gh CLI is not available.
httpx and python-dotenv must be installed.GITHUB_TOKEN must be set in .env.scripts/issue_manager.py must contain the create-pr command.To create a Pull Request from a source branch (e.g., develop) to a target branch (e.g., main):
python scripts/issue_manager.py create-pr \
--title "PR Title" \
--body "Detailed description of the changes" \
--head <source_branch> \
--base <target_branch>
python scripts/issue_manager.py create-pr \
--title "CHORE: Refactor Specs" \
--body "Consolidates specs and updates sync logic." \
--head develop \
--base main
Use when planning or operating a side project with GitHub issues and Notion only. Splits sources of truth, keeps active work small, and defines a low-overhead weekly and per-session routine.
Use when turning local work into a GitHub-backed change in this repository. Covers branch creation, issue linkage, push, and PR creation using local git plus scripts/issue_manager.py or direct GitHub API access.
Use when checking, creating, updating, syncing, or triaging GitHub issues in this repository via scripts/issue_manager.py and direct GitHub API reads.
Preserve existing links when editing Notion pages. Use for any request that updates Notion page content so edits are based on the current source and do not accidentally remove previously written links.
Use when creating or reorganizing `.specs` files in this repository. Keeps specs aligned with GitHub issue numbers, epic folders, and the current area-based directory layout.