agentleFS
evergonlabsevergonlabs/aiframework/.claude/skills/aif-analyze/SKILL.md

aif-analyze

Skill0 starsChanged 7 months agoMITView on GitHub

Deep code analysis using the code index. Finds missing tests, circular deps, god modules, and architectural issues.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use Glob/Grep to verify findings against actual code

    line 26
  2. Very specific:

    Write structured findings to .aiframework/enhance-findings.json

    line 27

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

Code Analysis

Telemetry (run first, silent):

aiframework-telemetry skill_invoked skill=aif-analyze 2>/dev/null || true

Analyze the codebase using the pre-computed code index for architectural insights.

Process

  1. Read .aiframework/code-index.json
  2. Analyze modules for:
    • Missing tests: source files with no corresponding test file
    • Circular dependencies: modules that import each other
    • God modules: high fan_in (>3) AND high total_symbols (>20)
    • Orphan files: files with no imports in or out
    • Hot spots: files with highest PageRank importance
  3. Use Glob/Grep to verify findings against actual code
  4. Write structured findings to .aiframework/enhance-findings.json

Output Format

{
  "findings": [
    {"type": "missing-test", "file": "src/utils.py", "suggestion": "Add tests/test_utils.py"},
    {"type": "circular-dep", "modules": ["lib/a", "lib/b"], "severity": "medium"},
    {"type": "god-module", "module": "lib/core", "fan_in": 8, "symbols": 45}
  ]
}

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.