Unified code review that fans out parallel scanners over a change — one per active lens, up to eleven per run — and merges them into one per-file report. Eleven lenses: comment quality, four quality/craft lenses (readability & tests, naming & module, objects & patterns, simplicity & types), an always-on correctness lens (wrong conditions, unhandled cases, off-by-one, swallowed errors, races, broken call contracts), an always-on narrow security lens (secrets, injection, access checks, boundary validation, insecure settings, IaC exposure, access widening, plus access policies and CI workflows), an always-on coherence lens (docs, contracts, migrations, config and sibling listings that disagree with the code or each other, code breaking a rule an accepted ADR or CONTEXT.md states), an always-on assumptions lens (code relying on library, runtime, CI or platform behaviour the installed source or the locked version contradicts, test doubles the real dependency would not match), a performance lens for executable source (N+1, unbounded fetch, blocking-in-async, wasted renders, missing indexes), and a spec lens via --spec <path> or a spec file the diff carries. Explicit rules in a root CODING_STANDARDS.md (plus a gitignored .local.md overlay) generate standards findings. The standalone comment-review and quality-review skills stay invocable for a single-lens pass. Reviews the current branch diff by default (or explicit paths / --base, or a GitHub PR with --pr). Quality findings are tagged family · rule · severity; comment verdicts are R1–R12 · KEEP/REMOVE/REWRITE/MOVE/ADD, shown side by side and applied through a single risk-cut menu. Successor to the comment-review and quality-review plugins.
Plugin code-review from marketplace cc-toolkit in grixu/cc-toolkit. Commands read from the repo's manifest — today.
comment-reviewCode review focused exclusively on comment quality — not logic, naming, or structure. Use when the user says "/comment-review", "review komentarzy", "sprawdź komentarze", "przejrzyj komentarze", "comment review", or asks to check whether comments in a change are worth keeping. Reviews the current br
cr-mergeHeadless last step of a code review that another workflow drives — merges the lens outputs cr-scan wrote into one re-graded report, writes it into the context directory, and returns every finding with its fix and risk class in a fixed line shape. Asks nothing and applies nothing. Not for interactive
cr-prepareHeadless first step of a code review that another workflow drives — resolves the committed change against a base, reads the project's conventions and standards once, decides the active lens set, and writes all of it to a context directory that cr-scan and cr-merge read. Asks nothing and edits nothin
cr-scanHeadless code-review Scanner for one lens, or a listed few in turn — reads the context directory cr-prepare or /start-cr wrote, judges the change against each lens's rules, and writes each lens's findings into the directory for cr-merge. Asks nothing and edits nothing. Not for interactive use: a per
quality-reviewCode review focused on code quality and craft — readability, structure, naming, object/state design, and needless complexity — not correctness, security, performance, or test coverage. Use when the user says "/quality-review", "review jakości", "sprawdź jakość kodu", "przejrzyj pod kątem jakości", "
/code-review:start-crExplicit-invocation orchestrator that runs the review lenses (comments, readability & tests, naming & module, objects & patterns, simplicity & types, correctness, security, coherence, assumptions, performance, spec) in parallel over a change and merges them into one per-file report. Lenses are gated
scannerCode-review Scanner — judges one change against one lens's rules, or a listed few in turn, by running the cr-scan skill over a context directory, and writes each lens's findings there. Internal sub-agent dispatched by /start-cr and by workflows that drive cr-prepare, cr-scan and cr-merge; not intend
Spec-driven delivery pipeline: grill a topic into ratified decisions, write and validate a spec against it, split the spec into dependency-ordered tasks, then implement them in isolated worktrees with batched validation.
5 skills · 2 commands · 3 agents
Easily create hooks to prevent unwanted behaviors by analyzing conversation patterns
2 skills · 4 commands · 1 agent · hooks
Audio/video transcription pipeline with summary, news extraction, and custom processing. Sources: YouTube URLs (yt-dlp) or local files (any format ffmpeg handles). Backed by ElevenLabs Scribe.
5 skills
Small everyday development skills: diagnose and fix failed CI pipelines, shepherd a pull request until CI is green and review is resolved, check a dependency upgrade against the codebase, and push a branch as a pull request filled from the repository's template and labelled with its risk, assessed by TypeSafe Jev, Gemini Decision or both.
4 skills
Deprecated — use fd3. End-to-end feature delivery: requirements gathering, editing, status tracking, and implementation orchestration with parallel subagents
4 commands
Proof that a pull request's change works: prepare-proof judges which proof a branch needs, with signals from TypeSafe Jev or Gemini Decision when a key is set, then produces each kind, a narrated walkthrough video with playwright-recast, screenshots at the project's breakpoints, and masked terminal or API transcripts, and hands it to pr-open through the branch's proof manifest.
4 skills
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.