← Browse

@bellini666/catchup

B

This skill should be used when the user asks to "catch me up", "what's on this branch", "summarize this branch", "what changed since main", or wants a structured summary of commits, changed files, and current state of the working branch compared to main/master.

skillclaude

Install

agr install @bellini666/catchup --target claude

Writes 1 file into .claude/skills/, pinned to git-bc1b3e94.

  • .claude/skills/catchup/SKILL.md

Document


name: catchup description: This skill should be used when the user asks to "catch me up", "what's on this branch", "summarize this branch", "what changed since main", or wants a structured summary of commits, changed files, and current state of the working branch compared to main/master.

Catchup: Branch Summary

Quickly understand what has changed in the current working branch compared to main/master.

Behavior

  1. Detect base branch (main or master)
  2. Detect platform (check for .gitlab-ci.yml → glab, otherwise → gh)
  3. Get commit log since divergence from base branch
  4. Get all changed files with git diff <base>...HEAD --stat
  5. Read changed files for context

Output Format

Commit Summary

  • List commits with their semver prefixes and short descriptions

Changes by Area

Group changed files into categories:

  • Migrations: new/modified database migrations
  • Config: settings files, CI config, dependency changes
  • Source: application code changes
  • Tests: new/modified tests

Key Changes

  • Highlight breaking changes or API modifications
  • Note new dependencies added (check pyproject.toml, package.json, Cargo.toml diffs)
  • Flag any renamed/moved files

PR/MR Context

  • If on a branch with an open PR/MR, show its title and status
  • Use gh pr view or glab mr view depending on detected platform

Current State

  • Any uncommitted changes
  • Potential issues or blockers

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-bc1b3e94bf7b2026-07-31