Create a planning document for pull requests against external repositories.
npx skills add https://github.com/Collectively-Gary/GaryOS --skill plan-code-pr
Please help me install this Agent Skill. Skill: plan / code-pr Source: https://github.com/Collectively-Gary/GaryOS/tree/main/data/skills/plan/code-pr Command: npx skills add https://github.com/Collectively-Gary/GaryOS --skill plan-code-pr
It prevents failed or off-convention pull requests by forcing a disciplined, repo-aware planning process before code changes are proposed.
Ask your agent to generate a code-pr playbook plan that clones the target repo, follows its contribution conventions for branching, and prepares an auditable gh pr create command with a deterministic approach and aligned test expectations.
High-intent search queries and answers about installing and using this skill.
To plan a pull request for an unfamiliar GitHub repository, you must clone and skim the target repo's README and CONTRIBUTING files first. This ensures your proposed code changes follow documented conventions before you execute any branch or `gh pr create` commands.
A deterministic approach for a GitHub pull request plan requires selecting exactly one implementation method at each decision point without offering alternatives. This discipline prevents ambiguous execution and ensures test assertions bind directly to the chosen approach.
To ensure your test plan matches your pull request approach, bind test assertions to the exact values or behaviors committed to in the selected approach. This prevents scope creep and aligns downstream verification with the planned code changes.
You prevent scope creep when contributing to external repositories by explicitly defining out-of-scope boundaries in your planning document. This enforces strict scope control and keeps your pull request focused on the original issue or PR comment.
Pull requests fail against external repo conventions when you skip context loading and propose code changes that ignore documented contribution guidelines. Enforcing a repo-aware planning process before submitting prevents these off-convention pull requests.
Yes, you need to read CONTRIBUTING.md before opening a GitHub pull request to an unfamiliar target repository. Mandated context loading ensures your branch names, commit messages, and `gh pr create` invocations match the repo's specific guidelines.
AlabamaMikeGuide users through Git branching, commits, pushes, and GitHub CLI pull requests for upstream skill contributions.
sakastudioCreate a GitHub pull request from the current branch using gh pr create.
Lev-itFetch and manage GitHub pull request review comments using the gh CLI.
mdmagnuson-creatorCoordinate ad-hoc software tasks with context loading, quality checks, and Git operations.
