agentleFS
ImtylerrrrrrImtylerrrrrr/second-brain/skills/analyze/SKILL.md

analyze

Skill1 starsChanged 5 months agoMITView on GitHub

Evidence-based deep analysis of one repo — onboards a stub into a real note, or verifies and corrects a drifted note. The only place milestone boxes get checked, always with citations. Use to onboard a repo, after a stale-thread warning, or when a note seems wrong.

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

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

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Every mark cites evidence inline.

    line 26

“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

second-brain: analyze

The evidence engine. Follow the discipline below EXACTLY — Part 2 governs this skill.

!cat "${CLAUDE_PLUGIN_ROOT}/references/discipline.md"

Steps

  1. Locate the vault (cwd or ancestors containing Projects/Dashboard.md; else registered vaults in ~/.claude/second-brain/vaults, ask if several; none → "run /second-brain:setup first"). Resolve the repo: the argument, else cwd, else ask. Locate its note in <vault>/Projects/ by frontmatter repo: match; missing → create from Projects/_TEMPLATE.md; auto-stub → this is an onboarding run.
  2. Read the evidence, in Part 2 order: README/docs → manifest → source tree → tests (run them only if cheap and safe — a test suite, not a deploy) → git -C <repo> log --oneline -30 → open PRs/issues via gh if available.
  3. Write the note:
    • ## 📌 One-liner from what the code actually is.
    • ## 🏁 Milestones with cited marks per Part 2 ([x] artifact+tests/commit · [~] partial, cite present AND missing · [ ] needs check).
    • Claims-vs-evidence contradictions recorded explicitly (e.g. "README claims billing ready; src/billing/stripe.ts is a stub with 0 tests → [~]").
    • frontmatter status + last_updated. Do NOT touch ## ▶ Thread or last_handoff_commit.
  4. Resolve TODO verification tasks left by end-session (confirm milestone "…"): verify each against evidence, mark the milestone accordingly with its citation, remove the TODO line.
  5. Update the Dashboard row: Status · Updated (fill Last session/Next only if the columns are empty — they belong to end-session).
  6. Report: what the evidence showed, every correction made, contradictions found — and invite the user to correct anything inferred.

Rules

  • Every mark cites evidence inline. No percentages. Code beats docs. Unknown → needs check. Never write to ## ▶ Thread.

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.