Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding.
This skill should be used when the user asks for a code review of a change — a pull request, merge request, branch, commit range, working-tree change, or pasted diff — covering correctness, security, performance, structure, and repository-specific rules. Trigger on phrases like "review this PR", "review this MR"…
Review a GitHub pull request and post one formal review — advance the existing discussion and give precision-first, high-signal feedback. Judgement on the diff, not a build gate — CI validates that it builds, and a targeted probe is allowed as evidence. Use when asked to review a PR or on a cron PR scan.
★not rated 22 3d agoASkillSpector: warn69 tokens
originalMIT
Catches state bloat, grab-bag models, and mutation ambiguity from AI coding agents. Use when reviewing state types, boolean flags, optional-field models, or mutable data patterns.
Analyze Ruby gem dependencies, vulnerabilities, outdated packages, maintenance health, and insecure gem sources with the gemtracker CLI. Use when asked to audit Ruby gems, check Gemfile.lock security, review dependency health, or run gemtracker.
Software quality review and design guidance for any code: naming, cohesion, coupling, duplication, function size, dependency direction, and testability. Use when someone asks to improve, review, refactor, or design code, or asks what good structure looks like here. Routes to the sub-skill matching the kind of work.
Review MCP server specifications and updates for compliance, security, and quality. Use when evaluating server.json files, PRs adding/updating servers, or assessing MCP server changes. NOT for creating new entries (use add-mcp-server instead).
A tool for turning code changes into a self-contained HTML report for a person to review. It explains the purpose, behavior, risks, compatibility, and evidence behind a difference in code.
A setup guide for adding the sgcop Ruby and Rails code-checking rules to a project. RuboCop is a tool that finds style and quality problems in Ruby code.
WHEN: User asks for a code quality audit, code review, or wants to find code smells, anti-patterns, or non-idiomatic Go code in their project. Also when asked "how good is this code?" or "audit my code." WHEN NOT: When the user wants to fix bugs, run tests, or just lint (use go-lint-audit for linting).
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
Project code-review style for this repo. Review the current branch's changes in two passes (correctness + justify-every-line), tracing any bug claim to ground before reporting.
Adversarial cross-model verification of work produced by an AI agent — code, documents, data, config, anything. A different model attacks the work against its brief, Claude arbitrates. Triggers on /verify-agent — or natural language like "verifica il lavoro che ha fatto l'agente", "è corretto quello che ha fatto…
Author a new project-specific Pythinker subagent (a specialist like "migration-reviewer" or "api-contract-checker") with a correct spec, a persona-rich system prompt, and a structured output contract. Use when the user wants to create, scaffold, or design a custom agent / subagent, or asks how Pythinker agent YAML /…
Use when maintaining open-source projects with AI assistance: issue triage, pull request review, release notes, maintainer automation, Codex for OSS application evidence, and privacy or safety guardrails for AI-assisted workflows.
Open a browser-based diff viewer showing all current changes in a VS Code-style file tree with syntax-highlighted diffs. Live-reloads as files change. Use when the user wants to "see the diff", "show changes", "what did I change", or "open diff viewer".
A coordination skill for handing an implementation plan to a separate coding process or remote machine, then tracking its progress. It uses the handoff command-line tool and supports independent executors such as Claude, Codex, or OpenCode.
★not rated 20▲
+1
changed 3d agoASkillSpector: pass216 tokens
originalApache-2.0
Run a human-feedback loop through RambleDesk. Hard trigger: when the user invokes /ramble, $ramble, [$ramble], or says to use RambleDesk/ramble feedback, create a RambleDesk request before answering the substance unless they explicitly say not to send one. Also use when real human judgment, review, approval, or…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: