agentleFS
JkudjoJkudjo/oh-my-cursor/skills/analyze/SKILL.md

analyze

Skill1 starsChanged 7 months agoMITView on GitHub

Deep codebase analysis — complexity, coupling, dead code, tech debt hotspots

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 52 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a large refactor — understand what you're dealing with

    line 13

“Common” is measured: kept by at least 6 in 10 of the 52 edited versions of this file we could read. “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

analyze

Invoke this skill for a structured analytical deep-dive into a codebase area.

When to use

  • Before a large refactor — understand what you're dealing with
  • Investigating performance issues
  • Finding tech debt hotspots
  • Understanding why something is complex or fragile

Analysis dimensions

  • Complexity — functions > 40 lines, deeply nested logic, cyclomatic complexity hotspots
  • Coupling — what depends on what, blast radius of changes
  • Dead code — unused exports, unreachable branches, zombie files
  • Tech debt — TODO/FIXME/HACK comments, workarounds, legacy patterns
  • Test coverage — which paths have no tests
  • Dependencies — outdated packages, circular imports, unnecessary deps

Output

## Analysis: {area}

### Summary
[3-sentence overview]

### Hotspots
- `file:line` — issue and why it matters

### Dependency map
[key relationships]

### Recommended actions
Priority 1: ...
Priority 2: ...

Saves to memory key analyze-{area} and artifact type=specs.

Download now (ZIP)

  • Other versions62 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 62

    1. anthropics/knowledge-work-plugins★ 34ksame name
    2. Yeachan-Heo/oh-my-codex★ 34ksame name
    3. oxsecurity/megalinter★ 2.6ksame name
    4. H-mmer/pentest-agents★ 815same name
    5. hardisgroupcom/sfdx-hardis★ 410same name
    6. nwiizo/tfmcp★ 373same name
    7. hsantanna88/clo-author★ 262same name
    8. hugosantanna/clo-author★ 262same name
    9. atelier-fashion/adlc-toolkit★ 173same name
    10. ArvorCo/Relentless★ 98same name

    52 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use constitution, revise and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • ArvorCoSkill

      constitution

      Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

      Also in 4 projects that use this

    • stormlightlabsSkill

      revise

      Address review comments on an open pull request and push the fixes. Use for /edit, /revise, or when asked to respond to review feedback on a PR number.

      Also in 3 projects that use this

    • ArvorCoSkill

      checklist

      Generate quality validation checklist from spec, plan, and tasks. Use after creating tasks. Triggers on: create checklist, quality checklist, validation checklist.

      Also in 4 projects that use this

    • DockerSkill

      write

      Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

      Also in 6 projects that use this

    • H-mmerSkill

      submit

      Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

      Also in 3 projects that use this

    • Itsokay-coSkill

      discover

      Automated pattern discovery — finds what correlates with your best and worst sleep nights. Scans workouts, meals, caffeine, tags, gut scores, and timing patterns. Use when the user wants to know what actually affects their sleep.

      Also in 5 projects that use this

    • +2 more from ArvorCo
  • In this repository22 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.