New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review Changes

by microbus-io in microbus-io/fabric

Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work.

Apache-2.0Auto-check passedBackend & APIs

Install Review Changes

skills CLI
$ npx skills add microbus-io/fabric --skill review-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microbus-io/fabric review-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/microbus/review-changes .claude/skills/review-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-changes
GitHub stars
172
Token cost
~1.8k tokens
SKILL.md length
782 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work.

  • Works in 5 steps: Resolve the Diff Scope → Map Changed Files to Microservices → Review Each Changed Microservice → …
  • Tasks that involve Microservices
  • Calls git

What it does

Review Changes is an agent skill from microbus-io/fabric. Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work. Runs the review-microservice skill on each changed microservice and the review-architecture skill scoped to those microservices and their graph neighbors, then consolidates one report. Use before merging a branch or before committing working-tree changes.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Microservices. It works with Git. The repository describes itself as: Microbus is the only fabric where every agentic workflow runs on a true microservice substrate - giving your workflows security, scale, observability, and prompt-driven authoring. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Microservices

Example prompts

  • “Use the review-changes skill to review the microservices touched by a set of changes - by default the whole current feature branch versus its…”
  • “/review-changes”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Resolve the Diff Scope
  2. Map Changed Files to Microservices
  3. Review Each Changed Microservice
  4. Architectural Review Scoped to the Changed Set
  5. Consolidate the Report

What it can do on your machine

Read from SKILL.md and the folder at commit fb98098. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Changes loads about 1.8k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 782 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~108
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microbus-io/fabric at commit fb98098, republished under its Apache-2.0 licence (© microbus-io). 782 words, ~1,785 tokens.

Download SKILL.mdSave it as .claude/skills/review-changes/SKILL.md (or your agent's skills folder).
name
review-changes
description
Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work. Runs the review-microservice skill on each changed microservice and the review-architecture skill scoped to those microservices and their graph neighbors, then consolidates one report. Use before merging a branch or before committing working-tree changes.
user-invocable
true

This skill composes the two review skills over a diff. It does not re-implement their checks - it resolves what changed, then drives review-microservice per changed microservice and review-architecture scoped to the changed set. The separation of concerns between the two is deliberate: per-microservice internals come from review-microservice, cross-cutting concerns from review-architecture, and this skill must not duplicate either.

Workflow

Copy this checklist and track your progress:

Change review:
- [ ] Step 1: Resolve the diff scope
- [ ] Step 2: Map changed files to microservices
- [ ] Step 3: Review each changed microservice
- [ ] Step 4: Architectural review scoped to the changed set
- [ ] Step 5: Consolidate the report
Step 1: Resolve the Diff Scope

Determine which files changed. The default depends on the current branch; an explicit argument overrides it.

First identify the current branch and the repository's default branch:

shell
branch=$(git rev-parse --abbrev-ref HEAD)
git status --porcelain                          # staged, unstaged, and untracked (always part of the scope)

Use the repository's actual default branch if it is not main (check git symbolic-ref refs/remotes/origin/HEAD or git remote show origin); substitute it for main below.

  • On a feature branch (not the default branch) - the default. Review the whole branch plus uncommitted work, the pre-merge review:
    shell
    base=$(git merge-base main HEAD)
git diff --name-only "$base" HEAD             # committed on this branch
    Union that with the working-tree list.
  • On the default branch (main) - there is no feature branch to diff, so default to the changes since the last tagged release, plus uncommitted work:
    shell
    tag=$(git describe --tags --abbrev=0 2>/dev/null)
git diff --name-only "$tag" HEAD              # only if a tag was found
    If git describe finds no tag (empty output / non-zero exit), fall back to reviewing the uncommitted work only.
  • uncommitted argument - regardless of branch, narrow to just the working tree (git status --porcelain, including untracked files) and skip any committed-diff.

If the resolved file list is empty, report that there is nothing to review and stop.

State the mode (branch-vs-default, since-last-release, or uncommitted-only), the base commit or tag, and the resolved file list to the user before proceeding.

Step 2: Map Changed Files to Microservices

For each changed file, walk up the directory tree to the nearest ancestor containing a manifest.yaml - that directory is the owning microservice. Collect the distinct set of changed microservices.

Also note, separately from that set:

  • Changes to main/main.go, config.yaml, env.yaml, or main/topology.mmd - these are application-composition changes that feed the architectural review in Step 4 even when no microservice directory changed.
  • Changes to framework packages (connector/, service/, application/, and the other library packages listed in the repository's root CLAUDE.md). These are out of scope for this skill, which reviews microservices. List them so the user knows they were seen and skipped, and suggest a plain code review for them.

Present the changed-microservice set and the out-of-scope list. If the set is empty but composition files changed, proceed to Step 4 only.

Show full SKILL.md (394 more words)Show less
Step 3: Review Each Changed Microservice

For each microservice in the changed set, run the review-microservice skill's full workflow on that directory, one microservice at a time, in this context. Do not launch subagents to review microservices in parallel unless the user explicitly asks to run the reviews concurrently or asks for a faster review; the default is sequential and in-context. Review the whole microservice, not only its changed files - a change frequently breaks or leaves stale something elsewhere in the same directory (a new endpoint that should have updated a shared helper, a renamed field a sibling handler still reads, a test that no longer covers the new path).

When ranking findings, put the ones that touch changed lines first; whole-service findings that predate this branch come after, labelled as pre-existing so the reader can tell regressions from latent issues.

Keep each microservice's findings under its own heading for the consolidated report.

Step 4: Architectural Review Scoped to the Changed Set

Run the review-architecture skill, but scope its findings. Build the full system map (Step 1 of that skill is cheap - it reads manifests), then focus the cross-cutting checks on:

  • the changed microservices, and
  • their immediate graph neighbors - the microservices that call them or that they call (from the downstream sections and *api imports). A change breaks coupling at the edges, so a neighbor one hop away is in scope; the rest of the system is context, not audited.

Prioritize the architectural checks most sensitive to a diff: newly introduced dependency cycles, new or removed downstream edges and whether the manifests still match the code, new events and their pairing, boundary shifts (an endpoint or table that moved between microservices), main/main.go startup-group ordering for added microservices, and cross-service workflow wiring when a workflow or task changed. Report system-wide findings that the changed set introduced or made worse; do not re-report unrelated latent architecture issues elsewhere in the system.

Step 5: Consolidate the Report

Merge the per-microservice reports from Step 3 and the scoped architectural report from Step 4 into one document. De-duplicate: if the same underlying issue surfaced in both a per-service and the architectural pass, keep the more specific statement once and drop the other. Order everything by severity (Critical, then Warning, then Info), and within a severity put change-introduced findings ahead of pre-existing ones.

markdown
# Change Review

## Summary
Scope (branch-vs-default, since-last-release, or uncommitted-only), the base commit or tag, the changed
microservices, and out-of-scope changes noted. Overall assessment and the count of findings by severity.

## Per-Microservice Findings

### {hostname}
(the review-microservice report for this microservice, change-introduced findings first)

(repeat for each changed microservice)

## Architectural Findings
(the review-architecture report, scoped to the changed set and its neighbors)

## Conclusion
Prioritized action items, change-introduced issues first.

Present the consolidated report to the user.

© microbus-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/microbus/review-changes of microbus-io/fabric.

Open the folder on GitHubat commit fb98098

Compare with similar skills

Review Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Changes this skillmicrobus-io/fabric172—~1.8kAutomated safety check: PassApache-2.0
Nuget UpdateCalabonga/Microservice-Template287—~1.4kAutomated safety check: PassMIT
Node Backend Development Guidelinesdiet103/claude-code-infrastructure-showcase10k2 repos~2kAutomated safety check: PassMIT
Nodejs Backend Patternsever-works/ever-works15818 repos~4kAutomated safety check: PassAGPL-3.0
Arcgis To Portaljsdatopian/portaljs2.4k1 repos~2kAutomated safety check: PassMIT
AWS Serverless Edazxkane/aws-skills3674 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • Nuget Update

    Calabonga/Microservice-Template

    Проверить и обновить версии NuGet-пакетов в активных шаблонах NET10.0 (Module, IdentityModule, RazorPages).

    287 GitHub stars~1.4k tokensUpdated 2 days ago
    Backend & APIsAuto-check passed

  • Node Backend Development Guidelines

    diet103/claude-code-infrastructure-showcase

    Sets layered architecture and coding rules for Node.js, Express and TypeScript microservices, covering routes, controllers, services, repositories, Prisma, Sentry and Zod.

    10k GitHub starsUsed in 2 repos~2k tokens
    Backend & APIsAuto-check passed

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    158 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed

  • Arcgis To Portaljs

    datopian/portaljs

    Migrate a whole ArcGIS Hub site into a PortalJS Arc portal end-to-end.

    2.4k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed

  • AWS Serverless Eda

    zxkane/aws-skills

    AWS serverless and event-driven architecture expert based on Well-Architected Framework.

    367 GitHub starsUsed in 4 repos~3.2k tokens
    Backend & APIsAuto-check passed

  • Golang Pro

    antoniopaya22/go-rest-template

    Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with…

    172 GitHub starsUsed in 3 repos~1.2k tokens
    Backend & APIsAuto-check passed

More from microbus-io/fabric

All 32 skills in this repo

  • Add Config

    microbus-io/fabric

    TRIGGER when user asks to add or modify a configuration property or setting, or to make a value configurable.

    172 GitHub stars~2.3k tokensUpdated 10 days ago
    Auto-check passed

  • Add Function

    microbus-io/fabric

    TRIGGER when user asks to add, create, or modify an API endpoint, function, or RPC, or a route that accepts typed arguments and returns typed results.

    172 GitHub stars~2.4k tokensUpdated 10 days ago
    Auto-check passed

  • Add Inbound Event

    microbus-io/fabric

    TRIGGER when user asks to listen for, subscribe to, or handle an event emitted by another microservice.

    172 GitHub stars~1.4k tokensUpdated 10 days ago
    Auto-check passed

  • Add Metric

    microbus-io/fabric

    TRIGGER when user asks to add or modify a metric, counter, gauge, or histogram, or to track/measure an operation.

    172 GitHub stars~1.5k tokensUpdated 10 days ago
    Auto-check passed

  • Add Outbound Event

    microbus-io/fabric

    TRIGGER when user asks to fire, emit, or publish an event that other microservices can subscribe to.

    172 GitHub stars~1.7k tokensUpdated 10 days ago
    Auto-check passed

  • Add Python Function

    microbus-io/fabric

    TRIGGER when user asks to add a Python-backed function endpoint to an existing Python-backed microservice.

    172 GitHub stars~1.3k tokensUpdated 10 days ago
    Auto-check passed

Works with

Categories

Questions about Review Changes

What does Review Changes do?

Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work. Review Changes is an agent skill from microbus-io/fabric. Reviews the microservices touched by a set of changes - by default the whole current feature branch versus its merge-base with main, plus any uncommitted work.

When should I use Review Changes?

Review Changes fits situations like: tasks that involve Microservices.

How do I install Review Changes in Claude Code?

Run `npx skills add microbus-io/fabric --skill review-changes -a claude-code`. Or copy the skill folder (.claude/skills/microbus/review-changes in microbus-io/fabric) into .claude/skills/review-changes in your project. Claude Code loads it when a task matches its description.

How do I install Review Changes in Codex?

Run `npx skills add microbus-io/fabric --skill review-changes -a codex`. Or copy the skill folder (.claude/skills/microbus/review-changes in microbus-io/fabric) into .agents/skills/review-changes in your project. Codex loads it when a task matches its description.

Can I use Review Changes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microbus-io/fabric --skill review-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-changes, .gemini/skills/review-changes, .github/skills/review-changes and .opencode/skills/review-changes in your project.

What does Review Changes need to run?

Going by SKILL.md and its folder, Review Changes needs the command-line tools its instructions call (git).

Does Review Changes access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review Changes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Changes use?

Review Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Changes use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review Changes?

Skills that share tags, products or a category with Review Changes: Nuget Update (Calabonga/Microservice-Template, 287 stars), Node Backend Development Guidelines (diet103/claude-code-infrastructure-showcase, 10k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars) and Arcgis To Portaljs (datopian/portaljs, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Changes?

microbus-io (a GitHub organization) maintains it in microbus-io/fabric, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on September 28, 2026.

Source: microbus-io/fabric on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.