code-reviewer
/code-reviewer
Code smell detector and refactoring advisor. Triggers on: file path mentioned, 'review this code', 'find smells', 'analyze', 'refactor', or code shared. Calls Episteme HTTP API (analyze + refactor endpoints) immediately. Outputs smell table, ranked refactorings, principle violations.
- Author
- epicsagas ↗
- Repository
- episteme ↗
- Licence
- Apache-2.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Code smell detector and refactoring advisor. Triggers on: file path mentioned, 'review this code', 'find smells', 'analyze', 'refactor', or code shared. Calls Episteme HTTP API (analyze + refactor endpoints) immediately. Outputs smell table, ranked refactorings, principle violations.
Triggers from the description
Original author description
Code smell detector and refactoring advisor. Triggers on: file path mentioned, 'review this code', 'find smells', 'analyze', 'refactor', or code shared. Calls Episteme HTTP API (analyze + refactor endpoints) immediately. Outputs smell table, ranked refactorings, principle violations.
How it works
- Prerequisites
SKILL.md preview
---
name: code-reviewer
description: "Code smell detector and refactoring advisor. Triggers on: file path mentioned, 'review this code', 'find smells', 'analyze', 'refactor', or code shared. Calls Episteme HTTP API (analyze + refactor endpoints) immediately. Outputs smell table, ranked refactorings, principle violations."
---
# Role
You review code and PRs by detecting smells via the knowledge graph, ranking refactorings, and citing the engineering principles behind each finding.
## Prerequisites
**Before any API call**, resolve the URL and token once:
```bash
eval $(epis api env)
# Sets: EPISTEME_URL=http://127.0.0.1:<port>
# Sets: EPISTEME_API_KEY=<token> (only if configured)
```
Then use `$EPISTEME_URL` and `-H "X-API-Key: $EPISTEME_API_KEY"` in all curl calls.
- API server must be running: `curl -sf $EPISTEME_URL/health` or start with `epis api start`
- Auth header (when key is set): `X-API-Key: $EPISTEME_API_KEY`
# Workflow
1. **Receive** code changes, PR description, or architectural proposal
2. **Detect** -- `curl -s -X POST $EPISTEME_URL/analyze -H 'Content-Type: application/json' -d '{"code":"...","language":"python"}'` to identify smells automatically
3. **Suggest** -- `curl -s -X POST $EPISTEME_URL/refactor -H 'Content-Type: application/json' -d '{"code":"...","language":"python","top_k":3}'` for ranked fixes per detected smell
4. **Map** -- `curl -s '$EPISTEME_URL/graph/ID?detail=full'` and `curl -s '$EPISTEME_URL/graph/ID/neighbors'` to connect smells to underlying principles
5. **Report** -- findings with entity citations, severity, and actionable fixes
# Code analysis
Pass code directly in the JSON body — no temp file needed:
```bash
# Detect smells
curl -s -X POST $EPISTEME_URL/analyze \
-H 'Content-Type: application/json' \
-d '{"code":"class GodClass:\n def create(self): pass\n def delete(self): pass","language":"python"}'
# Get ranked refactorings
curl -s -X POST $EPISTEME_URL/refactor \
-H 'Content-Type: application/json' \
-d '{"code":"class GodClass:\n def create(self): pass\n def delete(self): pass","language":"python","top_k":3}'
```
# Output Format
```
# Episteme Code Review
## Summary
[1-2 sentence overall assessment]
## Smell Detections
| Smell | Location | Severity | Related Principle |
|-------|----------|----------|-------------------|
| [Name] ([SMELL-xxx]) | [file:line] | [low/medium/high] | [LAW-xxx or DP-xxx] |
## Ranked Refactorings
1. **[Refactoring Name]** ([RF-xxx]) -- Priority: Critical
- Addresses: [SMELL-xxx]
- What to do: [concrete steps]
## Principle Violations
### [Entity Name] ([ID]) -- Violated
- **Violation**: [specific issue]
- **Fix**: [improvement via RF-xxx]
```
# Reference
For tool details and decision trees, see the `episteme` skill.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · epicsagas/episteme | 98 | Apache-2.0 |
| TerminalSkills/skills | 100 | Apache-2.0 |
| swap-cameroon/kuro-antigravity-config | 100 | MIT |
| a-pavithraa/springboot-skills-marketplace | 100 | MIT |
| borghei/Claude-Skills | 100 | MIT |
| nguyenthienthanh/aura-frog | 100 | MIT |
| yg-codes/srepowers | 100 | MIT |
| basamakcomtr/basamak-skills | 100 | MIT |
| criptogus/agent-evolve-network | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version cfbdb0b1fdd3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 98episteme
Software engineering knowledge graph — patterns, laws, refactorings, smells. Activates on any code quality concern, design decision, architecture review, or engineering question — even when the user describes problems informally. Uses Episteme HTTP API (resolved via `epis api env`) via curl. - 100episteme-researcher
Use this agent when you need to explore or research software engineering knowledge — finding design patterns, refactorings, laws, and code smells, or mapping relationships between concepts in the Episteme knowledge graph. - 100code-quality
Code review to find quality issues, style violations, and code smells. Triggers on: review, code review, quality, lint, code smell, analyze code. - 90smell
Run smell-reviewer against a file, directory, or the current working-tree changes. Use when someone says: check for code smells, smell review, find structural issues, review for smells, smell check, look for god classes, find long methods, check for dead code, smell this file,… - 100refactoring
Refactoring catalogs of Martin Fowler (Refactoring, 2nd ed.) and Joshua Kerievsky (Refactoring to Patterns): 29 code smells, 66 refactorings and 27 refactorings to patterns (Strategy, State, Command, Observer, Composite, Factory, Template Method...), each with mechanics, a C#… - 85smell-check
Runs a smell-first audit on a user-chosen path set: measures structure metrics, applies a named size profile, and reports code smells and test smells with evidence strength. Use for smell audit, code smell scan, whole-repo audit, tech debt scan, test smell check, maintainability…