submit
Skill2 starsChanged 6 days agoAGPL-3.0View on GitHub
Open every pull request through this skill — invoke it the moment completed changes need to become a PR, instead of running `git push` or `gh pr create` yourself, and once per PR in a stack. Never open a PR by hand while this skill is installed — it owns the branch and commit shape (Conventional Commits), the pre-push checks, the draft PR body (what, why, how), the mandatory screenshots for anything rendered, and the CI gate with root-cause fixes. Also triggers on "/submit", "submit this", "open a PR", "create a pull request", "push this up", "get this reviewed".
- Commits and pushes
11 other projects use a version of this.
Adopted by
Most recently taken up by
- huntie/skillstheir own version, first seen Nov 1, 2026
- tenex-labs/anthropic-claude-code-training-publictheir own version, first seen Oct 25, 2026
- snappedly/skillstheir own version, first seen Oct 13, 2026
- hsantanna88/clo-authortheir own version, first seen Oct 9, 2026
- hugosantanna/clo-authortheir own version, first seen Oct 8, 2026
- lablup/backend.aitheir own version, first seen Oct 8, 2026
Used with
Projects with it also use review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- H-mmer/pentest-agents★ 815same name
- lablup/backend.ai★ 679same name
- with-pebbly/aseprite-ai-artist★ 473same name
- hsantanna88/clo-author★ 262same name
- hugosantanna/clo-author★ 262same name
- JJFromTenex/claude-code-training★ 8same name
- snappedly/skills★ 2same name
- tenex-labs/anthropic-claude-code-training-public★ 2same name
- HimadriTrying/ai-job-search-agent★ 1same name
- huntie/skills★ 0same name
1 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
5 rules. 0 are common, 0 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 8 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.
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.