agentleFS
jhlee0409jhlee0409/proc-janitor/.claude/skills/analyze/SKILL.md

analyze

Skill7 starsChanged 9 months agoMITView on GitHub

Run a structured production-readiness analysis on the codebase

73 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constitution, revise and 10 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

  • 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

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 5 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

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read README.md and Cargo.toml for project overview

    line 12
  2. Distinctive:

    Read the file and analyze for:

    line 18
  3. Very specific:

    Append findings to analysis-report.md: after each module (incremental delivery)

    line 24
  4. Very specific:

    ALWAYS write to analysis-report.md incrementally — never wait until the end

    line 45
  5. Very specific:

    Run cargo clippy and cargo test as part of the analysis

    line 46

“Common” is measured: kept by at least 6 in 10 of the 63 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

Codebase Production-Readiness Analysis

Perform a structured production-readiness analysis of this project. Follow these steps:

Phase 1: Overview (First 2 tool calls)

  1. Read README.md and Cargo.toml for project overview
  2. List all source files in src/ and tests/
  3. Write initial overview to analysis-report.md immediately

Phase 2: Module-by-Module Analysis

For each source module in src/:

  1. Read the file and analyze for:
    • Security: Input validation, injection risks, unsafe code, error handling
    • Performance: Resource management, algorithmic efficiency, memory usage
    • Reliability: Error handling, edge cases, panic safety
    • Test Coverage: Existing tests, untested paths
    • Code Quality: Idiomatic Rust, clippy compliance, documentation
  2. Append findings to analysis-report.md after each module (incremental delivery)

Phase 3: Cross-Cutting Concerns

  • Dependency audit (outdated crates, known vulnerabilities)
  • Integration test coverage
  • Configuration validation
  • Deployment readiness

Phase 4: Final Report

Update analysis-report.md with:

  • Executive summary (3 sentences)
  • Categorized findings table:
    SeverityFileLineIssueRecommendation
    Critical............
    High............
    Medium............
    Low............
  • Prioritized action items (top 5)

Rules

  • ALWAYS write to analysis-report.md incrementally — never wait until the end
  • Run cargo clippy and cargo test as part of the analysis
  • Include exact file paths and line numbers for every finding

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.