agentleFS
thomas-powers-jrthomas-powers-jr/cadence/.claude/skills/pr-land/SKILL.md

pr-land

Skill2 starsChanged 53 days agoMITView on GitHub

Land a branch through cadence's protected-main pipeline — local preflight, commit hygiene, push, PR, babysitting the three required checks (ci-success, security-success, codeql-success), the known-flake protocol for test legs, consent-gated squash merge, and post-merge sync. Use when work is ready to land, the user says "land this", "open a PR", "merge when green", or a PR is sitting on CI.

  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. ten9876/AetherSDR★ 259same name
    2. Smirnov-Labs/claude-skills★ 6same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 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.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Run pnpm turbo run lint typecheck test build before pushing.

    line 16
  2. Very specific:

    Before any git operation that touches shared tree state — stash, reset, checkout onto main — re-check git status immediately beforehand, …

    line 21
  3. Very specific:

    Delete the local branch if --delete-branch didn't.

    line 77

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PR land (protected main)

main requires three status checks — ci-success (ci.yml), security-success (security.yml) and codeql-success (codeql.yml) — and enforce_admins is on, so there is no direct-push path, for anyone, and a red security or CodeQL run blocks the merge as surely as a red test leg. Everything lands branch → PR → green → squash merge.

1 — Preflight locally (cheaper than a CI round-trip)

  • Run pnpm turbo run lint typecheck test build before pushing.
  • Windows caveat: Linux CI is canonical. A few Windows-local test failures are known environment issues (pnpm/tempRepo/spawn races) — if something fails only locally and the failure smells environmental, push and let the CI matrix decide rather than debugging the dev box.
  • Before any git operation that touches shared tree state — stash, reset, checkout onto main — re-check git status immediately beforehand, not from a check done minutes earlier in this same session. Another process (a subagent, a background build, a second terminal) can have changed the tree in between.

2 — Commit hygiene

  • Stage explicitly, never git add -A. Off-limits: live .cadence/state.json
    • STATE.md dirt mid-loop (the settle commit owns those), .agents/, launch/ (local-only by explicit decision), .claude/scheduled_tasks.lock, stray uncommitted SESSION-*.md handoffs.
  • Single-commit settle convention when a phase is closing: source + tests + docs + phase artifacts land together in one commit, no separate chore: settle commit after it.
  • Feature PRs carry their .changeset/*.md. Conventional-commit subject with the phase id: feat: <what> (phase NNN).

3 — Push + PR

git push -u origin <branch>
gh pr create --title "<subject>" --body "<what/why, invariants checked>"

One logical change per PR. The PR body ends with the standard 🤖 Generated with [Claude Code](https://claude.com/claude-code) footer.

4 — Babysit CI (the flake protocol)

  • Watch with gh pr checks <n> --watch (or poll gh pr checks <n>).
  • On red, get the failing leg + test before reacting: gh run view <run-id> --log-failed | head -100.
  • Re-run once, without investigation, only when all three hold: a single OS/Node leg is red, the diff can't plausibly touch the failing area, and the failure matches a known flake (reference: macOS/Node22 timeout in settle-codereview-convergence.test.ts; new node --test subprocess spawns under parallel load have flaked before).
  • Anything else — multiple legs, plausible relation to the diff, an unfamiliar failure, or a second red after the re-run — is real until proven otherwise: investigate, don't loop re-runs.

5 — Merge (consent-gated)

  • Self-merging a PR this session opened requires the operator's explicit authorization — "merge it", "merge when green", or equivalent. A generic "continue" is not consent; when in doubt, report green and ask.
  • With consent: gh pr merge <n> --squash --delete-branch.

6 — Post-merge sync

git checkout main && git pull origin main
git log --oneline -3        # confirm the squash landed as expected
  • Delete the local branch if --delete-branch didn't; remove the phase worktree if one is now merged and idle.
  • cadence progress to confirm loop state, and update/write the handoff if this landing closes the session's unit of work.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.