agentleFS
dannys-code-cornerdannys-code-corner/incan/.agents/skills/review-code-smells/SKILL.md

review-code-smells

Skill73 starsChanged 5 days agoApache-2.0View on GitHub

Review touched code for maintainability smells such as duplication, awkward indirection, suspicious clones, dead code, poor naming, and Boy Scout cleanup opportunities. Use when a broad review needs a dedicated maintainability pass or when the user asks for code-smell review specifically.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a slice report at:

    line 30
  2. Very specific:

    Do not write to the canonical .agents/state/review-report.md.

    line 34
  3. Distinctive:

    Keep this pass practical. Do not invent refactors unrelated to the touched surface.

    line 44
  4. Distinctive:

    Keep slice reports findings-first.

    line 53
  5. Distinctive:

    If there are no findings, say so explicitly.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review Code Smells — Incan Compiler

Purpose

/review-code-smells is a file-focused report-only reviewer for local maintainability issues.

Own:

  • duplication
  • dead code
  • awkward or unnecessary indirection
  • suspicious clones
  • poor naming in touched code
  • touched-code cleanup opportunities that satisfy the Boy Scout rule

Do not own:

  • architecture-level placement decisions
  • docs truthfulness
  • test style details
  • final branch-clean judgment

Output artifact

Write a slice report at:

  • .agents/state/review-report.code-smells.md

Do not write to the canonical .agents/state/review-report.md.

Workflow

  1. Review the touched code files assigned by the orchestrator.
  2. Flag:
    • duplicated branches or helpers
    • no-op/unused/dead surfaces
    • awkward APIs or naming in touched code
    • needless complexity relative to the actual requirement
  3. Keep this pass practical. Do not invent refactors unrelated to the touched surface.
  4. Classify each finding as either:
    • maintainability
    • design-tension
    • or bug This classification is for downstream handling only. It must not be used to hide the finding.

Slice report shape

Keep slice reports findings-first. Only list clean surfaces when that clean call is non-obvious or useful for the orchestrator.

# Review Slice Report

- role: code-smells
- worker: <agent-id or stable label>
- status: in_progress | clean | blocked

## Scope
- assigned files:
  - loaves/toolchain/incan-cli/src/lib.rs

## Findings

- [ ] warning | maintainability | dead cli surface | loaves/toolchain/incan-cli/src/lib.rs:313
  `--bin` is exposed publicly but has no effect.

## Reviewed Clean Surfaces
- loaves/toolchain/incan-cli/src/commands/init.rs — maintainability reviewed; no findings

If there are no findings, say so explicitly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.