Push

Skill ryanjmichie-git/forgeproof-plugin/skills/push

Push a ForgeProof branch and open a pull request with provenance metadata embedded in the PR description. Use after running /forgeproof:run to create a PR from the generated code. Triggers on "push forgeproof", "create PR from forgeproof", or "open pull request with provenance".From its SKILL.md

Install

npx -y skills add ryanjmichie-git/forgeproof-plugin --skill push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.7 KB, as published. Nobody here has run it

ForgeProof Push: Branch & PR Creation

Create a pull request from a completed ForgeProof run with provenance metadata embedded in the PR description.

The provenance engine script is at ${CLAUDE_PLUGIN_ROOT}/skills/run/scripts/forgeproof.py (referenced as $FP below). Determine the Python interpreter once: run python3 --version; if that fails or reports Python is not found, use python. Set $FP_PY to whichever succeeded. The examples use bash syntax; if your shell is PowerShell, adapt the invocation (& $FP_PY $FP ...).

Step 1 — Identify the ForgeProof branch

Check the current branch:

git branch --show-current

If it matches forgeproof/<N>, extract the issue number. If not, look for recent forgeproof branches:

git branch --list 'forgeproof/*' --sort=-committerdate

Pick the most recent one (or ask the user if multiple exist). Set $ISSUE to the issue number.

If forgeproof/$ISSUE is not the current branch, check it out before continuing: git checkout forgeproof/$ISSUE — Steps 2-5 operate on the HEAD of this branch.

Step 2 — Verify bundle is committed at HEAD

The signed bundle must be part of the branch itself, not just the working tree — otherwise the pushed PR head has no provenance. Check:

git cat-file -e HEAD:.forgeproof/issue-$ISSUE.rpack

Success (exit 0) means the bundle is committed at HEAD — continue to Step 3.

If the check fails:

If .forgeproof/issue-$ISSUE.rpack exists on disk but is not committed, run the sealing commit from the run skill's Phase 4:
```
git add .forgeproof/ && git commit -m "forgeproof(#$ISSUE): seal provenance bundle"
```
Then re-run the Step 2 check above; it must succeed (exit 0) before you push.
If the file does not exist at all, tell the user to run /forgeproof:run $ISSUE first.

Step 3 — Push branch

First check if the remote branch already exists (from a previous run):

git ls-remote --heads origin forgeproof/$ISSUE

If the remote branch exists, force-push with lease to update it:

git push --force-with-lease -u origin forgeproof/$ISSUE

Otherwise, push normally:

git push -u origin forgeproof/$ISSUE

Step 4 — Generate PR body

Run the summary command to get the provenance table:

"$FP_PY" "$FP" summary --issue $ISSUE

Build the PR body with this structure:

Closes #$ISSUE

<summary output from above>

---
*This PR was generated with [ForgeProof](https://github.com/ryanjmichie-git/forgeproof-plugin). The `.rpack`
bundle in `.forgeproof/` is a cryptographically signed provenance record.
Run `/forgeproof:verify .forgeproof/issue-$ISSUE.rpack` to verify integrity.*
*The bundle can be verified automatically on PRs with the [forgeproof-verify GitHub Action](https://github.com/ryanjmichie-git/forgeproof-verify).*

Step 5 — Create PR

First check if a PR already exists for this branch (from a previous run):

gh pr list --head forgeproof/$ISSUE --state open --json number,url

If a PR already exists, update it instead of creating a new one:

gh pr edit <number> \
  --title "forgeproof(#$ISSUE): <concise description from commit>" \
  --body "<PR body from above>"

If no PR exists, create one:

gh pr create \
  --title "forgeproof(#$ISSUE): <concise description from commit>" \
  --body "<PR body from above>" \
  --base main \
  --head forgeproof/$ISSUE

Report the PR URL to the user.