Code review
Structured code review: correctness, security, tests; checks alignment with handoff and project docs when they exist.From its SKILL.md
npx -y skills add LaProgrammerie/ai-engineering-core --skill code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 323 tokens by cl100k_base, as published. Nobody here has run it
Code review (global)
Objective
Review a change systematically and return a prioritized action list without unsolicited large rewrites.
When to use
- Before merging a substantial PR or diff
- On explicit review request
Expected inputs
- Diff, file list, PR link, or change summary
- Stated intent or ticket (if any)
- Known constraints (perf, compatibility, security)
Steps
- Map touched files and stated or carefully inferred intent.
- Correctness: logic, errors, edge cases, API contracts, concurrency where relevant.
- Security: authz, injection, secrets, unsafe defaults.
- Tests: new paths covered, regression risk.
- Maintainability: coupling or readability only if it blocks evolution or reliability.
Documentation alignment (when the repo has it)
If project docs exist, verify consistency with:
docs/ai/active/handoff.md(or equivalent) — scope and allowed filesdocs/ai/02-architecture.md(or equivalent) — boundaries and patternsdocs/ai/03-standards.md(or equivalent) — conventions and commands
Call out drift between code and these documents as review findings.
Output format
- Summary in 2–4 lines
- P0 / P1 / P2 with location (file, symbol, or line when possible) and concrete suggestion
- No massive rewrite unless requested
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.