Conduct high-quality, persona-driven code reviews. Use when reviewing PRs, critiquing code quality, or analyzing changes for team feedback.
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.github/skills/common/common-code-review/SKILL.mdRole: Principal Engineer / senior review. Focus: logic, security, architecture. constructive.
FAIL returns CHANGES REQUESTED before semantic lens review. Missing, unknown, NOT RUN, or stale status is an evidence gap, never PASS.Use only [Blocker], [Major], or [Nit]. Each substantive finding has Evidence:, Why:, Fix:, and Prevent-by: lint | type | test | eval | runtime | guidance | none; missing code/diff means state the evidence needed. No praise section. See finding template.
HoangNguyen0403/agent-skills-standard
11c8bd1
Also appears in
since Sep 12, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.