steward
Skill2 starsChanged 33 days agoMITView on GitHub
Drive a Hoist pull request to green and ready to merge, covering which CI jobs run and what each checks, how to reproduce and fix a failing job, answering review comments, and the repository's conventions for branches, commits and PR descriptions. Use when opening a PR, when CI fails on one, when review comments arrive, or when asked to babysit or shepherd a PR.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- btraceio/btracetheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 16, 2026
- ForeactLabs/OpenExecutivetheir own version, first seen Nov 15, 2026
- 5thlayer/skillworkstheir own version, first seen Nov 8, 2026
- ElcanoTek/fleettheir own version, first seen Nov 8, 2026
- jmagly/kintsugi-usbtheir own version, first seen Nov 8, 2026
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- btraceio/btrace★ 6ksame name
- ForeactLabs/OpenExecutive★ 5.8ksame name
- SenteLabsAI/OpenExecutive★ 5.8ksame name
- richlander/dotnet-inspect★ 166same name
- mendixlabs/mxcli★ 139same name
- yschimke/compose-ai-tools★ 127same name
- antiv/mate★ 111same name
- michelbr84/GarraRUST★ 19same name
- jmagly/kintsugi-usb★ 18same name
- jmagly/carbonyl-agent★ 16same name
9 more not listed
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.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
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
- Distinctive: line 23
Read the failing job's log first and find the first error.
- Very specific: line 26
Run make ci again (and the job's own command), commit, and push to the PR's branch.
- Distinctive: line 27
Wait for the new run, and repeat until every job is green.
- Distinctive: line 34
When a comment asks for a change, make it in a new commit.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Taking a pull request to green
The jobs
| Workflow, job | Runs on | What it checks | Reproduce |
ci.yml check | every PR and push to main | cargo fmt --check, clippy with -D warnings, cargo test --all-targets, cargo test --doc, the API's TypeScript is current, rustdoc with -D warnings | make ci |
ci.yml ui | every PR and push to main | the console's UI: Prettier, ESLint, vue-tsc, Vitest, the build, and Playwright on the mock API (with axe-core's WCAG 2.1 A and AA rules on every page) and on the console over the fixtures | make ui-check, make e2e |
ci.yml msrv | every PR and push to main | cargo +1.88.0 check --workspace --all-targets --locked, and that Cargo.toml's rust-version is still 1.88 | make msrv |
ci.yml walkthrough | every PR and push to main | the quickstart, packaging/test-install.sh, shellcheck, scripts/walkthrough.py, scripts/http_check.py, the scripts' doctests and the benchmark tables' fixture | the check skill, step 2 |
ci.yml platforms | every PR and push to main | a --locked build on macOS 14 and Windows, and each binary's --version | not locally: read the log |
| coverage.yml | every PR and push to main | make coverage: line coverage at or above COVERAGE_MIN, and every line the PR adds run by a test. The LCOV report is the run's artifact | make coverage |
container.yml build | PRs and pushes to main that change the Dockerfile, .dockerignore, crates/, console/, the brand files the UI imports, the manifests, the quickstart or compose.yaml | both images build. In the CLI's, each binary, hoist doctor and the quickstart run. The console's starts healthy as the runner's user, refuses a request without its token, serves the built UI, and runs a doctor job | make docker, make docker-console |
| pages.yml | pushes to main only | the site builds with no dead link | make site, before merging |
The loop
- Read the failing job's log first and find the first error; later ones often follow from it. With the GitHub tools, list the PR's check runs and read the failed job's log.
- Reproduce it locally with the command in the table. The
checkskill explains each kind of failure. - Fix the cause, not the check. Do not weaken a test, a lint or the coverage threshold to get green unless the owner agrees, and then say so in the PR.
- Run
make ciagain (and the job's own command), commit, and push to the PR's branch. In a Claude Code on the web session, git can push only the session's branch. - Wait for the new run, and repeat until every job is green.
A job that fails without any change (a network error in npx, or a runner problem) can be re-run once. If it fails again, report it rather than retrying in a loop.
Review comments
- Answer each comment where it was made. Say what changed, with the commit, or why not.
- When a comment asks for a change, make it in a new commit. Keep the history readable, and do not force-push a branch someone is reviewing unless the owner asks.
- Resolve a thread only when the reviewer's point is addressed.
Conventions
- Branches: one purpose per branch, from main. Never push to main or force-push it; merging is the owner's call.
- Commits: the style of
git log. A subject that says what changed in plain words, with no type prefix and no final period (for example "Rustdoc: no links from public docs to private items"). The body is prose saying why and how, with a list when there are several parts. One logical change per commit, formatted and passingmake ci. - The PR description follows
.github/pull_request_template.md: What this changes (one or two sentences, and the issue it closes), How it was checked (tests run, and any replay or live run with its numbers and scope), and the checklist, ticked only for what was done. - In the same PR:
docs/cli.mdregenerated (make bless) when a command or option changed;docs/formats.mdfor a file format; the guide pages inwebsite/; CHANGELOG.md under Unreleased; and the claims ledger, if a quoted number changed (theresultsskill). - Writing: calm and exact, with every number's scope (brand/messaging.md). Hoist is always capitalised in prose; commands, crates and paths stay lowercase.
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.

