agentleFS
Sign inStart free
remembervictorchatbot-vipremembervictorchatbot-vip/AI_Token_Saving/skills/token-efficient-code-review/SKILL.md

token-efficient-code-review

Skill0 starsChanged 3 months agoMITView on GitHub

CONSOLIDATED. The token-efficient code-review retrieval engine (`crl`) now lives inside the unified `token-savings` skill at `$TOKS_SKILL_DIR/scripts/crl/`. Use the `token-savings` skill for all token-saving work, including code review (its PART C1/C2 + the `crl` path). This skill is kept only as a pointer to avoid duplicate/overlapping token-saving skills.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    All original mechanics (diff-aware closure retrieval, deterministic-first pre-flight, risk-ranked summary, staleness fingerprint, VBA …

    line 28

≈ “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

Token-Efficient Code Review — CONSOLIDATED into token-savings

This skill's retrieval engine (crl) has been folded into the unified token-savings skill. Do not maintain two token-saving skills.

What moved

  • scripts/crl/ (index / chunker / retrieve / analyze / preflight / tokens / cli) → $TOKS_SKILL_DIR/scripts/crl/
  • scripts/demo.py → $TOKS_SKILL_DIR/scripts/crl_demo.py
  • scripts/sample_repo/ → $TOKS_SKILL_DIR/scripts/sample_repo/

Use instead

Load token-savings and use its code-review path:

cd "$TOKS_SKILL_DIR/scripts"
python -m crl.cli index <repo>
python -m crl.cli review <repo> --changed app/utils.py --mode function --show
python -m crl.cli summary <repo> --files module.txt --top 12

All original mechanics (diff-aware closure retrieval, deterministic-first pre-flight, risk-ranked summary, staleness fingerprint, VBA support) are intact and verified (python crl_demo.py → 85% / 47% input saved).

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.

Check your setup, free