lead-review
Skill8 starsChanged 43 days agoNo licenceView on GitHub
The tech lead's review of a pull request against the project's own coding standards and review checklist, in any language. Discovers the repo's standards docs, checks out the PR branch in an isolated git worktree, runs the project's test / lint / format / type-check gates, proves each finding, then posts a review in a fixed, script-checked format that stays identical across rounds. Also audits commits pushed straight to a branch, as a range from a given commit or as one author's commits in it, with the rounds kept in a GitHub issue. Use when the user asks to review a PR, review a branch, re-review a PR after changes, review commits on main, review an author's commits since a hash, or do code review.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- snowfluke/my-tech-lead-flowword for word, first seen Sep 30, 2026
- rhonaldomaster/claude-skillstheir own version, first seen Sep 9, 2026
Other versions2 projects use a version of this.
Word for word · 1
- snowfluke/my-tech-lead-flow★ 8100% same
Edited · 0
None found.
Wrote their own version · 1
- rhonaldomaster/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.
In this repository19 other files it gives its agents.
- adopt-flowSkill
- api-specSkill
- coding-standardSkill
- deployment-planSkill
- github-project-initSkill
- groomingSkill
- init-claudeSkill
- product-discoverySkill
- project-docsSkill
- security-standardSkill
- task-breakdownSkill
- tech-lead-setupsSkill
- technical-specSkill
- test-auditSkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- troubleshootingSkill
- us-ac-formatterSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 11 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
11
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.