pr-ci
Skill83 starsChanged 12 days agoMITView on GitHub
Keep Headroom pull requests mergeable and their CI results true. Use before saying a pull request is green or ready, when a check fails or never starts, when a branch or stacked pull request falls behind main, or when a fork pull request waits for workflow approval.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- victor-falcon/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- victor-falcon/skills★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- app-api-compatibilitySkill
- provider-connectorSkill
- pr-showcaseSkill
- verify-webSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Run mise run mac:fixtures and mise run mac:contract when packages/view-model, apps/server/src/routes/app.ts or scripts/app-contract.ts …
- Very specific: line 50
Every required check, and macOS / ci when it applies, shows success on each pull request's head commit.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PR CI
"Green" means every required check ran on the pull request's head commit and passed. A green rollup can hide a missing run: on 2026-11-02 nine stacked pull requests showed only CodeQL after a fast multi-branch push, and CI had never run on them.
Check that CI ran
The main ruleset requires commits, check, binary-macos, site and image. A pull request that touches apps/macos also runs macOS / ci; it is not required, because its path filter would block other pull requests, but it must pass too.
sha=$(gh pr view <number> --json headRefOid -q .headRefOid)
gh api "repos/amitray007/headroom/commits/$sha/check-runs" -q '.check_runs[] | "\(.name) \(.conclusion)"'CodeQL alone is not CI. When a required check is missing on the head commit, close and reopen the pull request (gh pr close <n> && gh pr reopen <n>); the reopened event starts every workflow. A run that ends in startup_failure also needs a close and reopen; a rerun repeats the failure.
Bring a branch up to date
CI tests a pull request merged into its base, and the base keeps moving. When main changes a shared builder or the app feed, also rebuild the generated Mac files:
- Merge
origin/maininto the branch. A shared or stacked branch is updated by merges only, never rebased. - Run
mise run mac:fixturesandmise run mac:contractwhenpackages/view-model,apps/server/src/routes/app.tsorscripts/app-contract.tschanged on either side. - Push only after the check passes. When step 2 changed files:
mise run check && git commit -am "fix: regenerate the Mac fixtures and contract" && git push. Otherwise:mise run check && git push.
Stacked pull requests
A stack is managed with gh stack (gh stack view). Update it bottom-up: fix the lowest pull request that fails, then merge each branch into the one above it, running step 2 and step 3 at every layer. Merge the whole stack only with the owner's approval, in one atomic step: gh stack merge <stack> --merge --yes. The repository keeps delete_branch_on_merge off, so a merge one pull request at a time leaves the next one targeting a stale branch.
Fork pull requests
Workflow runs from a first-time contributor wait as action_required. Before approving, list what the pull request changes outside its code:
git fetch origin pull/<n>/head:refs/tmp/pr<n>
git diff --stat origin/main...refs/tmp/pr<n> -- .github scripts package.json bun.lock mise.tomlWith an empty result, approve: gh api -X POST repos/amitray007/headroom/actions/runs/<run-id>/approve. With any change there, ask the owner first. A new push from the contributor needs a new approval.
Workflows that push to main
The release bots push to main with the RELEASE_DEPLOY_KEY checkout key and [skip ci] in the bot commit message. A new workflow that pushes to main uses the same pattern (Pushes to main).
Done when
- Every required check, and
macOS / ciwhen it applies, showssuccesson each pull request's head commit. gh pr view <n> --json mergeStateStatusisCLEAN, orUNSTABLEonly from a check that is not required and that you reported.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

