push-to-forked-pr SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
push-to-forked-pr from hoangsonww/claude-code-agent-monitor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hoangsonww/claude-code-agent-monitor/push-to-forked-pr@git:20260819.69f8b2ePins git:20260819.69f8b2e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hoangsonww/claude-code-agent-monitor
- Path
.codex/skills/push-to-forked-pr/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260819.69f8b2e, committed Aug 19, 2026
- First version recorded
- Aug 19, 2026
- Size
- 9,117 bytes
- Repository stars
- 1,133
- License
- MIT
Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PR #N", "push to the forked PR", "update PR from fork", "push these changes to #N directly", "commit and push to the PR" — *especially* when they emphasise not creating a new branch or not pushing into the upstream repo. Use this **instead of** plain `git push…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# push-to-forked-pr The whole point of this skill: **`origin` is usually the upstream, but the PR's head is on someone else's fork.** Pushing to `origin` updates the upstream's branch, not the PR. You have to push to the fork. GitHub allows this in two situations: 1. You are the **fork owner** — straightforward, you own that branch. 2. You are an **upstream maintainer** and the PR has `maintainerCanModify: true` (the "Allow edits from maintainers" checkbox the PR author leaves on by default). GitHub then lets the upstream's auth push to the fork branch. If neither holds, abort and tell the user only the fork owner can push. --- ## Procedure ### 1. Read the PR's head metadata ```bash PR_NUMBER=<N> gh pr view "$PR_NUMBER" --json state,headRefName,headRefOid,headRepository,headRepositoryOwner,maintainerCanModify,url ``` Capture: - `state` — bail if not `"OPEN"`. - `headRepository.nameWithOwner` → the **fork** (e.g. `someone/Repo`). - `headRepositoryOwner.login` → the fork owner. - `headRefName` → the branch on the fork (usually matches local). - `headRefOid` → the PR's current head SHA. Your local HEAD must be a descendant. …
Read the whole file at its exact version.
How to install
mdr add hoangsonww/claude-code-agent-monitor/push-to-forked-pr@sha256:7a308a538365b612The line at the top of this page pins the label git:20260819.69f8b2e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_fzbcqmnc4rzfn35q)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Aug 19, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.69f8b2e latest | 2026-08-19 | 69f8b2e | 9,117 B | A | view · diff |
| git:20260819.14b9b60 | 2026-08-19 | 14b9b60 | 7,657 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9117 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hoangsonww/claude-code-agent-monitor · 1,133 stars · license MIT · pushed 2026-10-31 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_fzbcqmnc4rzfn35q GET https://markdownregistry.com/api/v1/resolve?ref=hoangsonww/claude-code-agent-monitor/push-to-forked-pr GET https://markdownregistry.com/api/v1/blob/7a308a538365b612b62666e92e572f788c644989f88ddcff94de5cabd4721d18
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hoangsonww/claude-code-agent-monitor
Every file in hoangsonww/claude-code-agent-monitor