gpsaggese/helpers / .claude/skills/github.create_child_pr
github.create_child_pr
VerifiedWrite instructions to build a child PR from the current branch
Goal
- Given the current
<SRC>Git branch, write instructions to build a child PR on a new<DST>branch
Workflow
Find the Next Branch Name
- Find which branch name is next available:
> i git_branch_next_name Found highest number '3' in all branches, next is '4' branch_next_name='HelpersTask1273_Get_Mac_tests_to_pass_4'
Create the Instructions File
- Create a file
plan-pr_merge.txtwith instructions to:- Create a
<DST>branch (e.g.,HelpersTask1273_Get_Mac_tests_to_pass_4) - Copy the files needed to merge PR2 from
github_PR_plan.mdfrom the current branch to the target branch - Create
plan-pr_commit_msg.txtwith the description of what the PR does - Create
plan-pr_title.txtwith the one line G - Create
plan-pr_pytest.shwith the tests that check the behavior of the PR - Add a comment for each phase, and make sure each command is correct
- Create a
- In
plan-pr_merge.txtandplan-pr_pytest.sh, state how they were generated, with this comment at the top of each file:# Generated by `.claude/skills/github.create_child_pr/SKILL.md`
Example
- Example commands to build a
pr_merge.txt:> export SRC_BRANCH=HelpersTask1273_Get_Mac_tests_to_pass > export DST_BRANCH=HelpersTask1273_Get_Mac_tests_to_pass_6 > git checkout master > git pull > i git_branch_create -b $DST_BRANCH > git checkout -b $DST_BRANCH > cat > pr_commit_msg.txt << 'EOF' Unit Test Infrastructure: Purification, Introspection, Numpy, and Base Updates - Adds new test purification module (hunit_test_purification.py) - Updates test infrastructure with new utility functions - Improves introspection module for better test support - Fixes numpy test compatibility issues - Updates base unit test module for macOS compatibility - All changes are related to test utilities and infrastructure improvements - Well-isolated changes to testing subsystem EOF # Copy the files through branches. > helpers_root/dev_scripts_helpers/git/git_sync_between_branches.sh --src_branch $SRC_BRANCH --dst_branch $DST_BRANCH --files "$FILES" # Copy the files from another dir. > export SRC_DIR=/Users/saggese/src/csfy1 > export DST_DIR=/Users/saggese/src/notes1 > export SUB_DIR=helpers_root > diff_to_vimdiff.py --dir1 $SRC_DIR/$SUB_DIR/ --dir2 ./$SUB_DIR/ > echo "$FILES" | tr ' ' '\n' > /tmp/file_list.txt > more /tmp/file_list.txt helpers/hunit_test_purification.py helpers/test/test_hunit_test_purification.py helpers/test/test_hintrospection.py helpers/test/test_hnumpy.py helpers/test/test_hunit_test.py > rsync -avR --files-from=/tmp/file_list.txt $SRC_DIR/$SUB_DIR/ $DST_DIR/$SUB_DIR/ > rsync -av $SRC_DIR/$SUB_DIR/ $DST_DIR/$SUB_DIR/ > git add $FILES > git commit -am pr_commit_msg.txt > cat > pr_pytest.sh << 'EOF' pytest \ helpers/test/test_hunit_test_purification.py \ helpers/test/test_hintrospection.py \ helpers/test/test_hnumpy.py \ helpers/test/test_hunit_test.py \ -v EOF > chmod +x pr_pytest.sh > FILES="helpers/hunit_test_purification.py helpers/test/test_hunit_test_purification.py helpers/test/test_hintrospection.py helpers/test/test_hnumpy.py helpers/test/test_hunit_test.py" > export CSFY_DOCKER_ENGINE="docker"; i docker_cmd --stage=local -v 1.6.0 --cmd "./pr_pytest.sh 2>&1 | tee build1.txt" > export CSFY_DOCKER_ENGINE="docker"; ./pr_pytest.sh 2>&1 | tee build2.txt > export CSFY_DOCKER_ENGINE="apple"; ./pr_pytest.sh 2>&1 | tee build3.txt > i gh_create_pr --no-draft > i gh_watch > pr_pytest.sh
Verification
- Confirm
plan-pr_merge.txt,plan-pr_commit_msg.txt, andplan-pr_pytest.shexist - Confirm
pr_pytest.shis executable and runs the correct tests - Confirm every phase has a comment and every command is correct
-
plan-pr_merge.txtandplan-pr_pytest.shsay they were generated by.claude/skills/github.create_child_pr/SKILL.md
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |