pre-review
Skill236 starsChanged 8 months agoApache-2.0View on GitHub
Check your branch before opening a PR (lint, test, title validation)
3 other projects use a version of this.
Adopted by
Most recently taken up by
- ai2cm/acetheir own version, first seen Oct 8, 2026
- LedgerHQ/ledger-livetheir own version, first seen Oct 8, 2026
- ffwright/claude-skillstheir own version, first seen Aug 17, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- LedgerHQ/ledger-live★ 628same name
- ai2cm/ace★ 261same name
- ffwright/claude-skills★ 0same 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.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
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
- Distinctive: line 16
Run local checks on the current branch before opening a pull request.
- Very specific: line 61
If source files changed, check for an entry in CHANGELOG.md under [Unreleased]
“Common” is measured: kept by at least 6 in 10 of the 3 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
Pre-review
Run local checks on the current branch before opening a pull request.
Steps
- Gather branch context
BRANCH=$(git branch --show-current) BASE="main" git log --oneline "$BASE"..HEAD git diff --stat "$BASE"..HEAD - Group changed files by area
- List files changed vs main
- Categorize: source (
arksim/), tests (tests/), docs (docs/), config, other
- Draft and validate title
- Infer type and scope from changes
- Propose a title matching:
^(feat|fix|docs|chore|ci|build|refactor|test|perf|style|revert)(\([a-z][a-z0-9_-]*\))?!?: .+$ - Verify max 72 characters
- Recommend a scope if omitted
- Run ruff check
ruff check . 2>&1 - Run ruff format check
ruff format --check . 2>&1 - Run unit tests
pytest tests/unit/ -x --tb=short 2>&1 - Check code quality in diff
- For new
.pyfiles in the diff, verify:# SPDX-License-Identifier: Apache-2.0header presentfrom __future__ import annotationspresent- Type annotations on function signatures
- Absolute imports only (no relative imports)
- For new
- Check changelog
- If source files changed, check for an entry in CHANGELOG.md under
[Unreleased]
- If source files changed, check for an entry in CHANGELOG.md under
Output
Print a readiness checklist:
Pre-review checklist
--------------------
[ ] Branch: <branch-name>
[x] Ruff check: PASS / FAIL (N issues)
[x] Ruff format: PASS / FAIL (N files)
[x] Unit tests: PASS / FAIL (N passed, N failed)
[x] License headers: PASS / FAIL / N/A
[x] Future annotations: PASS / FAIL / N/A
[x] Type hints: PASS / WARN / N/A
[x] Absolute imports: PASS / FAIL / N/A
[x] Changelog updated: YES / NO / N/A
[x] Suggested title: <title>
Ready to open PR: YES / NODoes 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.

