React Performance
affaan-m/ECC
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills).
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
Install Backend Code Review
$ npx skills add nazarli-shabnam/clevis --skill backend-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nazarli-shabnam/clevis backend-code-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nazarli-shabnam/clevis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/backend-code-review .claude/skills/backend-code-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "backend-code-review" agent skill from https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-review into .claude/skills/backend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-code-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nazarli-shabnam/clevis --skill backend-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nazarli-shabnam/clevis backend-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nazarli-shabnam/clevis.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/backend-code-review .agents/skills/backend-code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "backend-code-review" agent skill from https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-review into .agents/skills/backend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-code-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nazarli-shabnam/clevis --skill backend-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nazarli-shabnam/clevis backend-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nazarli-shabnam/clevis.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/backend-code-review .cursor/skills/backend-code-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "backend-code-review" agent skill from https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-review into .cursor/skills/backend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-code-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nazarli-shabnam/clevis.git --path .agents/skills/backend-code-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nazarli-shabnam/clevis --skill backend-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nazarli-shabnam/clevis backend-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nazarli-shabnam/clevis.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/backend-code-review .gemini/skills/backend-code-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "backend-code-review" agent skill from https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-review into .gemini/skills/backend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-code-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nazarli-shabnam/clevis backend-code-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nazarli-shabnam/clevis --skill backend-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nazarli-shabnam/clevis.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/backend-code-review .github/skills/backend-code-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "backend-code-review" agent skill from https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-review into .github/skills/backend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-code-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nazarli-shabnam/clevis --skill backend-code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nazarli-shabnam/clevis backend-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nazarli-shabnam/clevis.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/backend-code-review .opencode/skills/backend-code-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "backend-code-review" agent skill from https://github.com/nazarli-shabnam/clevis/tree/main/.agents/skills/backend-code-review into .opencode/skills/backend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backend-code-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
backend-code-review- GitHub stars
- 170
- Token cost
- ~1.5k tokens
- SKILL.md length
- 578 words
- Files
- 5 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
- Works in 4 steps: Security Review → Performance Review → Code Quality Review → …
- The user requests a review
- SKILL.md covers When to use this skill, How to use this skill, Checklist and General Review Rules, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Backend Code Review is an agent skill from nazarli-shabnam/clevis. Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., .py) under the api/ directory. Do NOT use for frontend files (e.g., .tsx, .ts, .js). Supports pending-change review, code snippets review, and file-focused review.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/architecture-rule.md`, `references/db-schema-rule.md` and `references/repositories-rule.md`).
It sits in Development, covering Code review, Customer feedback analysis and React components. It works with GitHub, PostgreSQL, FastAPI and Next.js. The repository describes itself as: Self-hosted GitHub security dashboard — tracks org security checks (MFA, branch protection, scanning) with score trends, plus automated Actions cache cleanup. FastAPI + Next.js +… The licence is GPL-3.0.
When your agent uses it
- The user requests a review
- Improvement of backend files (e.g.
- .py) under the api/ directory
- Frontend files (e.g.
Example prompts
- “/backend-code-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit d146b4f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Backend Code Review loads about 1.5k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 578 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nazarli-shabnam/clevis at commit d146b4f, republished under its GPL-3.0 licence (© nazarli-shabnam). 578 words, ~1,526 tokens.
Download SKILL.mdSave it as
.claude/skills/backend-code-review/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- backend-code-review
- description
- Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
Backend Code Review
When to use this skill
Use this skill whenever the user asks to review, analyze, or improve backend code (e.g., .py) under the api/ directory. Supports the following review modes:
- Pending-change review: when the user asks to review current changes (inspect staged/working-tree files slated for commit to get the changes).
- Code snippets review: when the user pastes code snippets (e.g., a function/class/module excerpt) into the chat and asks for a review.
- File-focused review: when the user points to specific files and asks for a review of those files (one file or a small, explicit set of files, e.g.,
api/...,api/app.py).
Do NOT use this skill when:
- The request is about frontend code or UI (e.g.,
.tsx,.ts,.js,web/). - The user is not asking for a review/analysis/improvement of backend code.
- The scope is not under
api/(unless the user explicitly asks to review backend-related changes outsideapi/).
How to use this skill
Follow these steps when using this skill:
- Identify the review mode (pending-change vs snippet vs file-focused) based on the user’s input. Keep the scope tight: review only what the user provided or explicitly referenced.
- Follow the rules defined in Checklist to perform the review. If no Checklist rule matches, apply General Review Rules as a fallback to perform the best-effort review.
- Compose the final output strictly follow the Required Output Format.
Notes when using this skill:
- Always include actionable fixes or suggestions (including possible code snippets).
- Use best-effort
File:Linereferences when a file path and line numbers are available; otherwise, use the most specific identifier you can.
Checklist
- db schema design: if the review scope includes code/files under
api/models/orapi/migrations/, follow references/db-schema-rule.md to perform the review - architecture: if the review scope involves controller/service/core-domain/libs/model layering, dependency direction, or moving responsibilities across modules, follow references/architecture-rule.md to perform the review
- repositories abstraction: if the review scope contains table/model operations (e.g.,
select(...),session.execute(...), joins, CRUD) and is not underapi/repositories,api/core/repositories, orapi/extensions/*/repositories/, follow references/repositories-rule.md to perform the review - sqlalchemy patterns: if the review scope involves SQLAlchemy session/query usage, db transaction/crud usage, or raw SQL usage, follow references/sqlalchemy-rule.md to perform the review
Show full SKILL.md (221 more words)Show less
General Review Rules
1. Security Review
Check for:
- SQL injection vulnerabilities
- Server-Side Request Forgery (SSRF)
- Command injection
- Insecure deserialization
- Hardcoded secrets/credentials
- Improper authentication/authorization
- Insecure direct object references
2. Performance Review
Check for:
- N+1 queries
- Missing database indexes
- Memory leaks
- Blocking operations in async code
- Missing caching opportunities
3. Code Quality Review
Check for:
- Code forward compatibility
- Code duplication (DRY violations)
- Functions doing too much (SRP violations)
- Deep nesting / complex conditionals
- Magic numbers/strings
- Poor naming
- Missing error handling
- Incomplete type coverage
4. Testing Review
Check for:
- Missing test coverage for new code
- Tests that don't test behavior
- Flaky test patterns
- Missing edge cases
Required Output Format
When this skill invoked, the response must exactly follow one of the two templates:
Template A (any findings)
# Code Review Summary
Found <X> critical issues need to be fixed:
## 🔴 Critical (Must Fix)
### 1. <brief description of the issue>
FilePath: <path> line <line>
<relevant code snippet or pointer>
#### Explanation
<detailed explanation and references of the issue>
#### Suggested Fix
1. <brief description of suggested fix>
2. <code example> (optional, omit if not applicable)
---
... (repeat for each critical issue) ...
Found <Y> suggestions for improvement:
## 🟡 Suggestions (Should Consider)
### 1. <brief description of the suggestion>
FilePath: <path> line <line>
<relevant code snippet or pointer>
#### Explanation
<detailed explanation and references of the suggestion>
#### Suggested Fix
1. <brief description of suggested fix>
2. <code example> (optional, omit if not applicable)
---
... (repeat for each suggestion) ...
Found <Z> optional nits:
## 🟢 Nits (Optional)
### 1. <brief description of the nit>
FilePath: <path> line <line>
<relevant code snippet or pointer>
#### Explanation
<explanation and references of the optional nit>
#### Suggested Fix
- <minor suggestions>
---
... (repeat for each nits) ...
## ✅ What's Good
- <Positive feedback on good patterns>- If there are no critical issues or suggestions or option nits or good points, just omit that section.
- If the issue number is more than 10, summarize as "Found 10+ critical issues/suggestions/optional nits" and only output the first 10 items.
- Don't compress the blank lines between sections; keep them as-is for readability.
- If there is any issue requires code changes, append a brief follow-up question to ask whether the user wants to apply the fix(es) after the structured output. For example: "Would you like me to use the Suggested fix(es) to address these issues?"
Template B (no issues)
## Code Review Summary
✅ No issues found.© nazarli-shabnam, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .agents/skills/backend-code-review of nazarli-shabnam/clevis.
- SKILL.md
- references/architecture-rule.md
- references/db-schema-rule.md
- references/repositories-rule.md
- references/sqlalchemy-rule.md
Open the folder on GitHubat commit d146b4f
Compare with similar skills
Backend Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Backend Code Review this skillnazarli-shabnam/clevis | 170 | — | ~1.5k | Automated safety check: Pass | GPL-3.0 | |
| React Performanceaffaan-m/ECC | 276k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Backend Code Reviewlangflow-ai/langflow | 155k | — | ~3.5k | Automated safety check: Notes | MIT | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Releasezmievsa/cadwyn | 309 | — | ~522 | Automated safety check: Pass | MIT | |
| Clean Code Refactorerfike/fastapi-blog | 101 | — | ~402 | Automated safety check: Pass | MIT |
Similar skills
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
Release
zmievsa/cadwyn
Prepare and publish Cadwyn releases. An agent skill from zmievsa/cadwyn.
Clean Code Refactorer
fike/fastapi-blog
Skill for identifying code smells and refactoring code using Clean Code, SOLID, and DRY principles.
Senior Fullstack
alirezarezvani/claude-skills
Fullstack development toolkit with project scaffolding for Next.js, FastAPI, MERN, and Django stacks, code quality analysis with security and complexity scoring, and stack selection guidance.
More from nazarli-shabnam/clevis
Andrej Karpathy Perspective
nazarli-shabnam/clevis
Andrej Karpathy的思维框架与表达方式。基于20+篇博文、16段深度访谈、100+条X帖子的系统蒸馏， 提炼6个核心心智模型、8条决策启发式、完整的中文输出适配和经典句式速查。
Related
Works with
Categories
Questions about Backend Code Review
What does Backend Code Review do?
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Backend Code Review is an agent skill from nazarli-shabnam/clevis. Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
When should I use Backend Code Review?
Backend Code Review fits situations like: the user requests a review; improvement of backend files (e.g; .py) under the api/ directory; frontend files (e.g.
How do I install Backend Code Review in Claude Code?
Run `npx skills add nazarli-shabnam/clevis --skill backend-code-review -a claude-code`. Or copy the skill folder (.agents/skills/backend-code-review in nazarli-shabnam/clevis) into .claude/skills/backend-code-review in your project. Claude Code loads it when a task matches its description.
How do I install Backend Code Review in Codex?
Run `npx skills add nazarli-shabnam/clevis --skill backend-code-review -a codex`. Or copy the skill folder (.agents/skills/backend-code-review in nazarli-shabnam/clevis) into .agents/skills/backend-code-review in your project. Codex loads it when a task matches its description.
Can I use Backend Code Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nazarli-shabnam/clevis --skill backend-code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backend-code-review, .gemini/skills/backend-code-review, .github/skills/backend-code-review and .opencode/skills/backend-code-review in your project.
What does Backend Code Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Backend Code Review is instructions for the agent only.
Does Backend Code Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Backend Code Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Backend Code Review use?
Backend Code Review is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Backend Code Review use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.
What are the alternatives to Backend Code Review?
Skills that share tags, products or a category with Backend Code Review: React Performance (affaan-m/ECC, 276k stars), Backend Code Review (langflow-ai/langflow, 155k stars), Code Review Skill (awesome-skills/code-review-skill, 2.1k stars) and Release (zmievsa/cadwyn, 309 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Backend Code Review?
nazarli-shabnam (a GitHub user) maintains it in nazarli-shabnam/clevis, which has 170 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: nazarli-shabnam/clevis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.