GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
Use when reviewing embedded C code for MISRA-C:2012 (Amendment 4, 2023) compliance, or when the user asks about MISRA rules, embedded C safety, ISR safety, or wants a static-analysis-style review without commercial tools like IAR C-STAT or Axivion. Triggers on phrases like "MISRA review", "is this safe for embedded"…
Tour is a local code-walkthrough CLI for AI agents. After finishing a task, the agent leaves line-anchored comments on a pinned git diff (a guided traversal) that a human steps through in a TUI or webapp. Activates when the user asks to "review this branch", "review this PR", "walk me through this diff", "leave…
Use when asked about a rebar repo's health, compliance, tier, or contract status — and before claiming any tier, badge, or "green" state in docs or commits. Runs the three status surfaces and reads them without conflating the two maturity vocabularies.
Use when opening, reviewing, or merging a pull request. Covers pre-PR checks (linting, tests, branch naming), PR description requirements, and post-merge cleanup. Not for code review commentary or architecture decisions — use the relevant role guidelines for those.
A project-documentation synchronisation workflow for rebuilding project facts from a local Git folder, GitHub repository, or current working directory, then updating core workflow documents.
Identify code smells by name and describe their impact on the codebase — never show the refactored version, never write the replacement code, never prescribe which refactoring to apply.
A review skill that checks an implementation against its tasks, written requirements, project rules, supporting knowledge, tests, and—when relevant—its design.
★not rated 5
changed 3d agoASkillSpector: pass70 tokens
originalMIT
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Take one feature request from prompt to reviewed, audited delivery in a SINGLE autonomous pass — one runnable Workflow that plans, reviews the plan, builds task by task, cross-reviews the build, and optionally runs a launch audit, then RETURNS the verified findings rather than looping (the user decides any fix round…
Review, explain, or assess the Pull Request represented by the currently checked-out feature branch in a local git repository. Use for requests such as "review this PR", "explain this PR", "what does this PR do", or "review the current branch". Produce an evidence-backed, interactive single-file HTML dashboard with an…
Review a GitHub pull request using an opinionated, collaborative review style. Trigger when the user asks to review a PR, check a PR, or look over a PR.
Analyze code for code smells from the Fowler / Beck / Kerievsky catalog (including the Industrial Logic Smells-to-Refactorings reference), then refactor them away one by one using named refactorings from Fowler's Refactoring and Kerievsky's Refactoring to Patterns. Each smell is fixed in isolation with a…
Analyzes newly-added or significantly-modified types in a pull request for invariant strength, encapsulation, and enforcement. Produces 1-10 ratings on encapsulation/expression/usefulness/enforcement with concrete improvement suggestions. Use when reviewing PRs that introduce or substantially change types, classes…
Technical Debt Scanner — Scan any codebase for TODOs, FIXMEs, duplicated logic, unused exports, oversized files, circular dependencies, and code smells. Generates a prioritized debt report with estimated effort. Use when the user asks to: (1) audit technical debt, (2) find TODOs or FIXMEs, (3) detect code duplication…
Get a second opinion from Codex CLI (OpenAI) on plans, code, or debugging. Use this skill when the user asks to review plans with Codex, get a code review from Codex, or wants a second perspective on a bug. Also use proactively: after finishing an implementation plan, after completing a feature implementation, or when…
Use when Claude has written a plan and the user wants codex to verify it against the actual codebase — runs gpt-5.5 and gpt-5.4 at xhigh reasoning in parallel with full shell access, iterates until both converge. Strict prompt-level prohibition on destructive operations. Prefer /codex-review for fast, deterministic…
Process review comments on an MR, a design doc, or a spec — validate each finding independently with parallel validator subagents, apply fixes for the ones that hold up, and produce a reply report designed to earn reviewer sign-off. The report explains exactly how each confirmed issue was fixed, and for anything not…
Use this skill whenever you need to explore, search, or understand code — including code reviews, PR analysis, architecture review, finding definitions or references, tracing call graphs and dependencies, assessing the impact of changes, discovering API routes or MCP tools, searching by concept, or understanding file…
★not rated 5 2d agoA145 tokens
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: