Skip to content
Skills Library
AI & agents · Review & audit

show-changes

/show-changes

Present completed work to the human for optional review via the ai-review desktop app. Use when you've finished a task and want the human to see what you did — they can optionally leave feedback.

Repository
ai-review ↗
Licence
MIT
Last repository change
21.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 21.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Present completed work to the human for optional review via the ai-review desktop app. Use when you've finished a task and want the human to see what you did — they can optionally leave feedback.

Original author description

Present completed work to the human for optional review via the ai-review desktop app. Use when you've finished a task and want the human to see what you did — they can optionally leave feedback.

How it works

  1. Steps
  2. Notes
Original SKILL.md headings · 59 lines, 456 words
SKILL.md preview
---
name: show-changes
description: Present completed work to the human for optional review via the ai-review desktop app. Use when you've finished a task and want the human to see what you did — they can optionally leave feedback.
---

You have completed a task and want to show the human what you did. Open ai-review so they can look over the changes and optionally leave feedback. This is less formal than a full code review — the framing is "here's what I did" rather than "please review my code."

## Steps

1. **Determine what to show.** Check these in priority order to pick the right `air` invocation:

   a. **Uncommitted changes exist** (staged or unstaged, check via `git status --porcelain`):
      Run `air --wait --json` with no branch/commit flags. This shows the working directory diff.

   b. **All changes committed, on a gg stack branch** — the current branch matches the `user/name` pattern (no `--` in the name part) and `.git/gg/config.json` exists:
      Read the gg base branch from config (parse `defaults.base`, fall back to `main`). Run:
      ```
      air --wait --json --commits <gg-base>..HEAD
      ```
      This shows the full stack diff, matching what ai-review displays when opening a gg stack.

   c. **All changes committed, on a feature branch** (not main/master):
      Determine the base branch (`main` or `master`, whichever exists). Run:
      ```
      air --wait --json --branch <base-branch>
      ```

   d. **All changes committed, on main/master itself:**
      Identify the first commit you made during this session. If you can determine the exact commit, use that hash directly. Otherwise, fall back to the first unpushed commit: run `git log origin/main..HEAD --oneline --reverse` (or `origin/master`) and take the first commit hash. Run:
      ```
      air --wait --json --commit <first-relevant-commit-hash>
      ```

   e. **None of the above:** Run `air --wait --json` with no flags (empty diff — the app handles it).

   The `air --wait --json` command opens the ai-review desktop app and blocks until the human submits. They may add comments or submit with no comments. The output is structured JSON.

2. **Handle the response.**

   - **If the human submitted comments:** Parse the JSON feedback. The output has the shape:

     ```json
     {
       "format": "ai-review.feedback/v1",
       "context": { "mode": "...", ... },
       "comments": [
         { "id": "...", "file": "...", "startLine": 10, "endLine": 12, "side": "old|new", "text": "...", "createdAt": "..." }
       ]
     }
     ```

     Address each comment: read the referenced file and lines, make the requested change. If a comment is unclear, use your best judgment.

   - **If the human submitted with no comments:** (empty `comments` array) Acknowledge that they've seen the changes and move on.

3. **Summarize.** If changes were made, provide a concise summary listing each comment and what you did to address it.

## Notes

- If `air` is not found, tell the user to install via `brew install --cask mrmans0n/tap/ai-review` (macOS) or build from source at https://github.com/mrmans0n/ai-review.
- If the diff is empty, inform the user there are no changes to show.
- Do NOT commit after making changes — let the user decide when to commit.

Versions

The database has no other skills named show-changes.

Database snapshot: 13.11.2026 · package version 08cbea41c0fe (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100human-review
    Request human code review via the ai-review desktop app. Use when code changes are complete and ready for a final human review before committing or merging. Opens an interactive diff viewer where the human can leave inline comments, then returns their feedback.
  • 100deepline-plays-review
    Use this skill when a human needs to review a Deepline Play result and hand feedback, labels, or approval back to the agent for revision, evaluation, comparison, or bounded iteration. Triggers on “put this run in a Sheet,” “review these results,” “read my feedback,” “make this a…
  • 100review-commits
    Open existing commits in the ai-review desktop app for review. Use when you need to review, understand, or get feedback on specific commits, a commit range, or a branch diff — not your own recent work, but existing history.
  • 96task-debrief
    Use when the user invokes a task debrief to verify the agent's completed work and audit its child agents, time, logged model cost, and workflow lessons in a private report.
  • 90agent-delegation-protocol
    Decide what to hand to an agent, what to keep with a human, and what to split, based on reversibility and consequence rather than capability alone. Use when deciding how much of a workflow to automate.
  • 100eval-review
    Interactive review of evaluation results. Presents judge scores and skill outputs for human feedback, then proposes SKILL.md improvements based on what the user identifies. Use when the user wants to review eval results, look at results, check scores, see what went wrong, give…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.