adrianj98-skills

A reviewer that assumes your code is wrong, in a context window that never saw you write it. Split-context review modelled on Bun's Zig-to-Rust rewrite.

1 skill · 1 agent · hooks

Light caveman mode: short, plain, filler-free replies for the rest of the session. Code, errors and technical terms stay exact; warnings stay in full sentences.

1 skill

Finds the AI slop in what just changed — restating comments, defensive checks on trusted values, dead abstraction, inflated prose — reports it, and on request cuts it.

1 skill

Pulls an AlertD server's diagnostics by its short name with alertd-core's npm run alertd-server, remembers each name's URL after the first time, and with only a name works out what is wrong from the diagnostics alone.

1 skill

Questions an analysis or diagnosis the AI gave: splits it into claims, checks the load-bearing ones in a fresh context, names the explanations it skipped, and says what holds, what's wrong and what was never verified.

1 skill

Says what it will do and lists the workflows it will watch, then merges the default branch into the current branch, pushes, reruns the PR's required integration check when it was skipped, and fixes the code when a check fails. A skill only, no script.

1 skill

Where a branch and its pull request stand: what it's about, then its state — review, checks, conflicts, what's unpushed, and the one thing left before it merges.

1 skill

Point it at a file, type, table, field or feature and it explains how that data is stored and used — where it lives, its shape across layers and where the shapes drift, who writes it, who reads it, how it moves, and when it dies.

1 skill

A very short list of what you worked on since your last working day, from the commits in every worktree of the current repo, your GitHub PRs, your Jira issues and any aj-log.md.

1 skill

A highly visual code walkthrough, always published as an artifact: a clickable diagram of the path the change takes, a file map with +/- bars, then 3–8 short stops each with a locator, a diagram or before/after panel, annotated code, a file:line and why. Defaults to the PR branch; also takes a description that focuses the tour or picks the code to tour.

1 skill

A band above the prompt in any GitHub repo: the branch, the PR and its checks, the changed files, and per repo, set in ~/.claude/work-band.json with /wb settings or /wb setup, the Jira issue and a dev-server button.