agentleFS
Sign inStart free
michael-denyermichael-denyer/black-box-unlock/skills/analyze/SKILL.md

analyze

Skill2 starsChanged 34 days agoMITView on GitHub

Analyze the repository for code hotspots and forensic signals with bbu. Use when the user asks which parts of the codebase are unstable, risky, or worth refactoring first.

70 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

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

  • 0

    Common

    Most of the 60 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run a forensic analysis of this repository using the bbu CLI:

    line 6
  2. Very specific:

    If the command fails with "gh" related warnings, re-run with --no-ci.

    line 9
  3. Very specific:

    If bbu is not installed, tell the user: uv tool install black-box-unlock, then retry.

    line 10
  4. Very specific:

    If the black-box-unlock MCP server is connected, get_hotspots, get_coupled_files, get_ownership, and get_flaky_steps return this evidence …

    line 24

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

Run a forensic analysis of this repository using the bbu CLI:

  1. Run: bbu analyze-repo --output=json --days=90
    • If the command fails with "gh" related warnings, re-run with --no-ci.
    • If bbu is not installed, tell the user: uv tool install black-box-unlock, then retry.
  2. Parse the JSON. Report, in order:
    • Top 5 hotspots by hotspot_score (commits x indentation complexity), with their bugfix_commits and build_failures counts.
    • Coupled pairs: files whose coupled_with entries have rate_to_partner >= 0.5, hidden dependencies; changing one without the other is a defect source.
    • High-risk ownership: files where is_high_risk is true (more than three authors and no one holding half the commits).
    • Flaky steps from flaky_steps, if any.
  3. Recommend which 2 or 3 files deserve refactoring or extra review first, and why. Ground every recommendation in the numbers you just reported.

If the black-box-unlock MCP server is connected, get_hotspots, get_coupled_files, get_ownership, and get_flaky_steps return this evidence without parsing JSON. Pass days=90 to the first three; their default window is 30 days, and get_flaky_steps always uses 30. Every result carries provenance naming the HEAD it read.

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