#code-review
214 resources · page 2 of 4
Results
- go-ultimate
The complete Go development skill.
- pr-reviewer
Use when the user asks to review, audit, comment on, or 评审 / 审查 a GitHub Pull Request
- audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality.
- brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements.
- catchup
Summarize and review what changed while you were away.
- cc-changelog
CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations).
- codex-loop
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR.
- docs-check
CONTRIBUTOR TOOL - Validate plugin against latest Claude Code documentation.
- full
Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review.
- session-deep-dive
Deep qualitative analysis of high-signal sessions.
- ui-ux-review
Audits an existing rendered interface or frontend diff for hierarchy, content clarity, interaction states, accessibility, responsive behavior, visual…
- elixir-writing-docs
Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata.
- exunit-code-review
Reviews ExUnit test code for proper patterns, boundary mocking with Mox, and test adapter usage.
- go-web-expert
Comprehensive Go web development persona enforcing zero global state, explicit error handling, input validation, testability, and documentation…
- llm-artifacts-detection
Detects common LLM coding agent artifacts in codebases.
- pytest-code-review
Reviews pytest test code for async patterns, fixtures, parametrize, and mocking.
- rust-testing-code-review
Reviews Rust test code for unit test patterns, integration test structure, async testing, mocking approaches, and property-based testing.
- strategy-interview
Act as a strategy interviewer who helps the user produce a strategy document grounded in the kernel framework (diagnosis, guiding policy, coherent action), enhanced with three complementary lenses applied when the conversation warrants them
- strategy-review
Pressure-test strategy documents to find where they'll break before reality does it for you.
- tdd
Guides test-driven development — decomposes a feature or bug fix into testable behaviors, then runs Red-Green-Refactor cycles with a…
- codeql
Run CodeQL database creation and security queries, add data-extension models, or process CodeQL SARIF.
- fp-check
"Is this bug real?" or "is this a true positive?" - "Is this a false positive?" or "verify this finding" - "Check if this vulnerability is…
- insecure-defaults
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production.
- sharp-edges
Identify error-prone APIs, dangerous configuration, and footgun designs that enable security mistakes.
- vuln-report
Turn one confirmed security finding into a disclosure-ready GitHub advisory with root cause, proof of concept, impact, and source evidence.
- adr-writing
Generate Architectural Decision Records (ADRs) following the MADR template with systematic completeness checking.
- review-renovate
Review Renovate bot PRs that update GitHub Actions dependencies.
- OCR Review-to-Approval Loop
Drive a PR to an approved code review by looping OCR's multi-agent review and address steps.
- prun
Use prun when the task splits into independent units that can run at once (different modules, separate research questions, parallel…
- permissions
Configures Claude Code permissions for safe agent autonomy.
- post-code-review-to-pr
Run a full pull request review and post review comments directly to the current branch's GitHub PR.
- lark-slides
The publisher’s description is only a heading. Open the skill to read what it does.
- chinese-git-workflow
The publisher’s description is only a heading. Open the skill to read what it does.
- api-pagination
Implement correct, fast API pagination — cursor vs offset trade-offs, opaque cursor encoding, stable sort keys, page-size limits,…
- caching-strategies
Deep reference for caching — what to cache, cache-aside vs read/write-through/write-behind, TTLs with jitter, eviction (LRU/LFU/FIFO),…
- git-collaboration-workflows
Run git collaboration that scales — trunk-based vs git-flow decided by deploy cadence, branch protection and required checks, PR sizing and…
- owasp-top10
A deep prevention reference for the OWASP Top 10 web risks — broken access control, injection, crypto failures, insecure design, SSRF and…
- readme-writing
How to write a README that gets a project understood and running fast — lead with what/why, a 60-second quickstart, then usage, config, contributing, and…
- rest-api-design
Conventions for designing clean, consistent, evolvable REST APIs — resource modeling, HTTP semantics, status codes, pagination, filtering,…
- secure-auth
Implement authentication securely — authentication vs authorization, password hashing (argon2id/bcrypt), sessions vs JWT (storage, expiry,…
- sql-index-tuning
Diagnose slow SQL queries and add the right indexes without over-indexing — B-tree mechanics, composite ordering (equality-before-range),…
- vanara-orchestrate
Run a goal end-to-end as a gated pipeline of specialist agents — reproduce → test → patch → review → commit — where nothing advances past a gate until its…
- vanara-route
Given a task, find the best-fit installed Vanara agent and run it.
- my-router
Context-aware router that detects work type and dispatches to the right skill.
- readme-polish
A README is a text wall with no visual anchors and no one can tell what the project does from a first glance.
- architectural-analysis
Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns,…
- architectural-decision-record
Create, extract, or convert an ADR (architectural decision record) using the ADR template.
- code-overview
Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or…
- code-walkthrough
Walks a person through code changes one step at a time in conversation, starting at the entry point and following the flow that changes, showing a small…
- coding-standard
Creates and updates coding standards, conventions, rules, and guidelines for the current project.
- design-an-api
Designs the contract for an API change inside one codebase — a component's props, a function surface, URL or query parameters, an event payload, or a…
- manual-test-planning
Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section…
- project-discovery
Discovers the core attributes of the current code repository and its projects — languages, frameworks, tooling, and where things live — and writes a…
- project-documentation
Creates and maintains project documentation for features, systems, and components.
- runbook
Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live…
- work-items-to-jira
Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project.
- challenge-plans
Before you execute a drafted plan/spec/design doc, run a multi-agent adversarial cross-review to surface the flaws that cause downstream rework,…
- continuous-feedback
Identifies improvement targets from accumulated session learnings and proposes concrete skill/agent modifications.
- harness-writing
> 🌐 [English version](https://github.com/tienenwu/fables/blob/main/en/harness-writing/SKILL.md) · 繁體中文（正本 / canonical）
- codebase-orientation
Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change…
