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

review-change

Skill2 starsChanged 35 days agoMITView on GitHub

Review the current branch, index, or working tree with calibrated repository evidence from bbu. Use before opening a PR or when the user asks what to check in a change.

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-change, implement-change and 7 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.
  • BanKnightSkill

    plan-change

    将已完成 spec/design 的 change 拆成可执行 plan 与 tasks。用户要把设计落成执行计划、任务清单或实现步骤时使用。

    Also in 7 projects that use this

  • Codagent-AISkill

    implement-change

    Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.

    Also in 7 projects that use this

  • MaheshAwasareSkill

    write-runbook

    Generate an operational runbook for a service from its code, config, and dependencies — what to do when it breaks, where to look, how to roll back, who to escalate to. Use proactively before a service goes to production, after a major incident, or when handing off operational ownership.

    Also in 3 projects that use this

  • testified-ossSkill

    incident-triage

    Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.

    Also in 4 projects that use this

  • srclightSkill

    refactor-safely

    This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.

    Also in 3 projects that use this

  • Google CloudSkill

    open-pr

    Commits local changes to a new Git branch and opens a GitHub pull request through the configured GitHub MCP server. Use when proposing code changes in a new pull request. Don't use for local-only commits without a remote GitHub repository.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Run bbu review-change --base origin/main, or call the review_change MCP tool with mode="base" and base_ref="origin/main" when the …

    line 8
  2. Very specific:

    If origin/main is not the intended upstream, use the base named by the user.

    line 12
  3. Very specific:

    Use --profile NAME when .bbu.toml defines a profile for this review.

    line 17
  4. Very specific:

    Use --include-ci only when failed GitHub workflow evidence is useful.

    line 18
  5. Very specific:

    Treat an empty action list as a valid clean result.

    line 22

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

Review the change that is about to ship:

  1. Run bbu review-change --base origin/main, or call the review_change MCP tool with mode="base" and base_ref="origin/main" when the black-box-unlock server is connected. The tool's default mode is working_tree, which skips branch commits.
    • If origin/main is not the intended upstream, use the base named by the user.
    • For index-only review, run bbu review-change --staged.
    • For unstaged and untracked work only, run bbu review-change --working-tree.
    • Use --profile NAME when .bbu.toml defines a profile for this review.
    • Use --include-ci only when failed GitHub workflow evidence is useful.
  2. Report the returned actions in order. Preserve the exact paths, raw revision counts, directional coupling rate, and ratio_lower_bound, the 95% lower bound of the symmetric ratio.
  3. Treat an empty action list as a valid clean result. Do not invent extra recommendations or turn the evidence into a composite risk score. If omitted_actions is non-zero, say how many candidates the cap dropped.
  4. Mention whether CI was disabled, available, partial, or unavailable. When an inspect_ci_failures action is present, link the returned run and say that its changed paths are implicated, not proven causal.
  5. Repeat any warnings the result carries, such as a shallow clone.

The command applies the selected profile, project path-role rules, support floor, deterministic ordering, and three-action cap. History before a rename counts toward the current path.

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