pr
Skill11 starsChanged 10 days agoApache-2.0View on GitHub
Pre-PR quality gate — run /code-review --fix on the branch diff before opening or updating a pull request. Trigger on "open a PR", "create a pull request", "ready for review", "/pr", or when about to push a branch for review.
- Commits and pushes
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ciao-dev-installSkill
- ciao-release-notesSkill
- ciao-releaseSkill
- ciao-upkeepSkill
- gws-sharedSkill
- gws-workflow-email-to-taskSkill
- gws-workflow-file-announceSkill
- gws-workflow-meeting-prepSkill
- gws-workflowSkill
- gws-workflow-standup-reportSkill
- gws-workflow-weekly-digestSkill
- persona-content-creatorSkill
- persona-customer-supportSkill
- persona-event-coordinatorSkill
- persona-exec-assistantSkill
- persona-hr-coordinatorSkill
- persona-it-adminSkill
- persona-project-managerSkill
- persona-researcherSkill
- persona-sales-opsSkill
- persona-team-leadSkill
- recipe-backup-sheet-as-csvSkill
- recipe-batch-invite-to-eventSkill
- recipe-block-focus-timeSkill
- recipe-bulk-download-folderSkill
- recipe-collect-form-responsesSkill
- recipe-compare-sheet-tabsSkill
- recipe-copy-sheet-for-new-monthSkill
- recipe-create-classroom-courseSkill
- recipe-create-doc-from-templateSkill
- recipe-create-events-from-sheetSkill
- recipe-create-expense-trackerSkill
- recipe-create-feedback-formSkill
- recipe-create-gmail-filterSkill
- recipe-create-meet-spaceSkill
- recipe-create-presentationSkill
- recipe-create-shared-driveSkill
- recipe-create-task-listSkill
- recipe-create-vacation-responderSkill
- recipe-draft-email-from-docSkill
- recipe-email-drive-linkSkill
- recipe-find-free-timeSkill
- recipe-find-large-filesSkill
- recipe-forward-labeled-emailsSkill
- recipe-generate-report-from-sheetSkill
- recipe-label-and-archive-emailsSkill
- recipe-log-deal-updateSkill
- recipe-organize-drive-folderSkill
- recipe-plan-weekly-scheduleSkill
- recipe-post-mortem-setupSkill
- recipe-reschedule-meetingSkill
- recipe-review-meet-participantsSkill
- recipe-review-overdue-tasksSkill
- recipe-save-email-attachmentsSkill
- recipe-save-email-to-docSkill
- recipe-schedule-recurring-eventSkill
- recipe-send-team-announcementSkill
- recipe-share-doc-and-notifySkill
- recipe-share-event-materialsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 10
Before opening or updating a pull request, run this gate.
- Distinctive: line 15
Inspect: Read the applied edits with git diff.
- Very specific: line 16
Open or update the PR: only after step 2 (gh pr create / push / update).
- Very specific: line 23
Only skip /code-review if it is genuinely absent from the environment (check with the Skill tool / /help) — say so explicitly and do the …
≈ “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.
Files
PR quality gate
Contributor/project skill — lives in the repo's workspace
skills/folder, notciao/stock/skills/. It is for people working on Ciaobot and is deliberately not packaged or shipped to end-user installs.ciao sync-skillsmirrors it into the runtime-discovered.claude/skills/catalog. Don't move it intociao/stock/.
Before opening or updating a pull request, run this gate. Do not open the PR until findings are applied or explicitly deferred with the user.
Steps
- Review + apply. Invoke
/code-review --fixon the branch diff (commits ahead of upstream plus uncommitted changes). Pass a higher effort for large or risky diffs. If the diff touches auth, secrets, or external input, runsecurity-reviewinstead (or in addition). - Inspect. Read the applied edits with
git diff. Keep, amend, or discard (git add -p/git checkout -- .) before committing anything the review wrote. - Open or update the PR only after step 2 (
gh pr create/ push / update).
Optional after the PR exists: /code-review --comment posts findings as inline PR comments.
Notes
/code-reviewalready covers reuse, simplification, and efficiency findings. Do not also require/simplifyunless you specifically want a cleanup-only autofix without a bug hunt.- Only skip
/code-reviewif it is genuinely absent from the environment (check with theSkilltool //help) — say so explicitly and do the equivalent review by hand. - Release cuts use the same gate on a wider range; see
skills/ciao-release/SKILL.md.
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.

