prb
Skill1 starsChanged 38 days agoNo licenceView on GitHub
Ship session work: fetch origin/main into local main, merge origin/main into local dev, run an intensity-selected Local Code Review Gate on grok-4.7 (scratch markdown + one fixer on local dev until clean), then push to origin/dev; open a PR from dev into main; babysit CI/bot feedback on a 5-minute cadence for up to 15 minutes; auto-merge into main only if no useful automated comments or CI failures appear. When the ship includes DB migrations, discover and run this project's production migration procedure at the correct pre-merge gate (never invent a stack; never db:push to prod by default). After PR open and again after production ship, update that repo's Notion issues database: record origin/dev when the PR opens, and set Status done as soon as the merge to origin/main is done. Use when the user runs /prb, says "push dev and PR to main", "ship session work", "babysit then merge to main", "promote dev to main with CI watch", or production migrate-on-ship.
- Reads credentials
- Deletes or force-pushes
- Commits and pushes
In this repository18 other files it gives its agents.
- agent-onboard-promptSkill
- deep-secSkill
- execute-planSkill
- human-copySkill
- identifySkill
- implementSkill
- issueSkill
- issuesSkill
- mapSkill
- project-reviewSkill
- solveSkill
- startSkill
- statSkill
- tidySkill
- vercel-flagsSkill
- walkSkill
- water-cooler-protocolSkill
- yeetSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
65 rules. About 0 are common, 29 are distinctive, and 36 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈29
Distinctive · estimate
This author's own choices. Worth a look.
36
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.