Professional code review skill: identify defects, security risks, and best practice violations. Use when asked to review, audit, or improve code quality.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Code Review
You are an experienced code reviewer. When asked to review code:
**Standard workflow:**
1. Read the code carefully, looking for issues across all dimensions
2. Load the review checklist via `read_skill_resource("code-review", "references/checklist.md")`
3. Analyze the code against each checklist item
4. Prioritize findings: Critical > High > Medium > Low
5. Provide specific fix suggestions with example code
**Focus areas:**
- Security vulnerabilities (SQL injection, XSS, authentication flaws, etc.)
- Logic errors and boundary conditions
- Performance issues (N+1 queries, unnecessary loops, etc.)
- Code maintainability and readability
**Available references:**
- `references/checklist.md` — Complete review checklist (security/performance/quality)
- `references/style_guide.md` — Code style reference
The line at the top of this page pins the label v2.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_7hhzhsumpxaz66xi
GET https://markdownregistry.com/api/v1/resolve?ref=echoyue-lp/echo-agent/code-review
GET https://markdownregistry.com/api/v1/blob/152dddcb0a4860a0754bf79f8845e41f34e0f3b81f693756de4eb68acd226086
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
echoyue-lp/echo-agent · echo-agent-learning/examples/demo_skills/data-analyst/SKILL.md · Data analysis skill: statistical analysis, data interpretation, and visualization recommendations. Use when asked to…
echoyue-lp/echo-agent · echo-agent-learning/examples/demo_skills/project-stats/SKILL.md · Analyze project structure, count lines of code by language, find TODOs/FIXMEs, and generate project health summaries…
echoyue-lp/echo-agent · echo-agent-learning/examples/demo_skills/python-linter/SKILL.md · Lint and format Python files using ruff. Activates automatically when Python files are touched. Use to check code…
echoyue-lp/echo-agent · echo-agent-learning/examples/demo_skills/web-researcher/SKILL.md · Web research skill: systematically collect, verify, and synthesize information from multiple sources. Use when asked to…
agno-agi/agno · cookbook/02_agents/16_skills/sample_skills/code-review/SKILL.md · Code review assistance with linting, style checking, and best practices
kyegomez/swarms · examples/single_agent/capabilities/skills/multiple_skill_dirs/team_skills/code-review/SKILL.md · Review Python code for bugs, missing tests and security issues using the team's shared standards
basicmachines-co/basic-memory · .agents/skills/code-review/SKILL.md · Use when reviewing Basic Machines code for house style, architecture risk, pre-merge hardening, or whether a change…
nteract/semiotic · .github/skills/code-review/SKILL.md · Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence. Use for GitHub…