Review & quality
19,178 rows, by stacks then stars
1,766 of these skill files have been read, by 1,273 distinct authors, and what they tell an agent counted. What Review & quality authors agree on, and what they forbid
richfrem/agent-plugins-skills/plugins/cli-agents/skills/agt-security Skill
5★ repoProvides sandboxing validation, HMAC key rotation, and budget verification to manage security boundaries under Agentic Group Theory (AGT).
richfrem/agent-plugins-skills/plugins/dev-utils/skills/context-bundler Skill
5★ repoInteractively creates targeted code, design, and documentation bundles for external review (Markdown or ZIP). Includes a comprehensive library of review & delegation persona templates (Adversarial Security, Plan Critique, Refactoring Quality, Sub-Agent Task Handoff, Documentation Synthesis, Architecture, Compliance).
richfrem/agent-plugins-skills/plugins/dev-utils/skills/convert-mermaid Skill
5★ repoTranslate .mmd diagram files into PNG images with configurable resolution (retina/HQ/scale), supporting rasterization (raster, rasterize, rasterization). V2 includes L5 Delegated Constraint Verification via verify_png for strict binary linting and Puppeteer-based rendering.
richfrem/agent-plugins-skills/plugins/dev-utils/skills/link-checker-agent Skill
5★ repoSpecialized Quality Assurance Operator for documentation link integrity and scans. Automatically handles automated link validation, auditing, fixing, and repairing broken documentation links and docs paths across repositories, with guidance on when to commit changes.
richfrem/agent-plugins-skills/plugins/obsidian-wiki-engine/skills/obsidian-wiki-linter Skill
5★ repoRuns a semantic health check over the Obsidian LLM wiki using the cheapest available LLM CLI. Finds inconsistencies, missing concepts, stale articles, connection candidates, and new article suggestions. Writes a structured report to meta/lint-report.md. Use when the wiki is large enough to have quality drift, or as a periodic maintenance step.
AnmarHani/SwarmVault/skills/swarm-implement Skill
5★ repoImplementation phase — turn a validated design into dependency-ordered tickets, then work them as one of N parallel agents with atomic claims, model tiering, and tests-in-ticket definition of done. Use to plan tickets from a design, pick up/continue implementation work, coordinate parallel agents, or check what to build next.
AnmarHani/SwarmVault/skills/swarm-review Skill
5★ repoMilestone review sweep — a strong model audits everything since the last sweep against the spec: requirement fulfillment, standards, simplification, risk. Use when a milestone's tickets are done, before opening the next milestone, or when asked to review/audit/validate completed work.
SkillMedev/skills/skills/changelog-writer Skill
5★ repoTranslates raw engineering release notes - commits, tickets, PR titles - into a user-facing changelog grouped as New, Improved, and Fixed, with a highlights section on top, benefit-first phrasing in the user's vocabulary, bugs described by their symptoms, and internal-only churn cut and flagged. Use when someone says "write the changelog for this release", "turn these commit messages into release notes users can read", "announce what shipped this week", or their changelog currently reads as internal jargon. Do NOT use for auto-generating a technical changelog from git history for developers - use changelog-generator instead.
The same file is in 1 other repository
SkillMedev/skills/skills/citation-tracker Skill
5★ repoVerifies that every citation is real, unretracted, and complete, rates source quality by evidence tier, and formats reference lists precisely in APA, MLA, Chicago, or IEEE. Use when someone asks "check my references", "format this bibliography in APA", "are these citations real", or "convert my reference list to IEEE". Do NOT use for checking whether the claims in the text are true - use fact-checker or claims-verifier instead. Do NOT use for writing the review itself - use literature-review or systematic-review instead.
The same file is in 1 other repository
SkillMedev/skills/skills/claims-verifier Skill
5★ repoDecomposes a claim into checkable propositions, traces each through the citation chain to its primary source, appraises the evidence for method and independence, and issues a verdict from Supported to Contradicted with confidence. Use when someone asks "is this claim actually backed by the study it cites", "verify the claims in this whitepaper", "trace this statistic to its source", or needs an evidentiary audit of research, marketing, or policy claims. Do NOT use for a quick true/false corroboration of a discrete factual statement - use fact-checker instead; for broad open-ended investigation of a topic, use deep-research instead.
SkillMedev/skills/skills/code-review-checklist Skill
5★ repoRun a systematic multi-pass code review - correctness, design, security, performance, tests - and report findings ordered by severity with concrete, respectful suggestions. Use when someone asks "review this PR", "review this diff", "what's wrong with this change", or wants a pre-merge quality gate on a branch. Do NOT use for a security-only deep audit of a change - use secure-code-review instead - or for writing the ticket or tracking artifact that describes the change - use jira-ticket-writer instead.
The same file is in 1 other repository
SkillMedev/skills/skills/coverage-gap-finder Skill
5★ repoProduces a risk-ranked list of untested critical paths and branches from a real branch-coverage report crossed with git churn, naming the specific missing cases and the smallest test that buys the most safety. Use when someone says "we have 85% coverage but I don't trust it", "what should we test next", "audit the suite before this release", or "which coverage gaps actually matter". Do NOT use to prove existing assertions are strong - covered-but-unasserted lines are mutation-test-runner's job; do NOT use to pin the current behavior of legacy code before a refactor - use characterization-test-writer instead. This skill decides what to test and in what order, not how well a test asserts or how to lock down legacy.
The same file is in 1 other repository
SkillMedev/skills/skills/deep-research Skill
5★ repoRuns a thorough multi-source research process - decompose the question, gather independent sources, cross-check, synthesize - and delivers a structured, cited brief with confidence levels and gaps. Use when someone asks "research this topic in depth", "give me everything on X", "what does the evidence say about Y", or needs a broad question answered from secondary sources with citations. Do NOT use for designing a study that collects new data - use primary-research instead; for distilling an already-gathered pile of 20+ sources into themes, use research-synthesis; for verifying one discrete claim, use fact-checker.
The same file is in 1 other repository
SkillMedev/skills/skills/design-critique Skill
5★ repoRuns a structured design critique of a screen, flow, or component across three dimensions - jobs-to-be-done, clarity, and delight - and delivers a severity-ranked critique table with one prioritized recommendation. Use when someone asks "critique this design", "review this mockup before we build it", "this flow feels off but I can't say why", "which design debt matters", or a new design or redesign is up for review. Do NOT use for verifying a built implementation against its spec - use design-qa-checklist instead; for planning moderated usability sessions, use usability-test-plan.
SkillMedev/skills/skills/employment-contract Skill
5★ repoReviews an employment agreement clause by clause, flags deviations from market-standard terms - non-compete scope, IP assignment breadth, cause definitions, equity mechanics - and produces a review table with recommended asks, explicitly bounded as not legal advice. Use when someone asks "can you review my offer letter", "is this non-compete normal", "what does this IP assignment clause mean", "should I push back on this severance term", or has an employment agreement in hand before signing. Do NOT use for negotiating the compensation number itself - use salary-negotiation instead - or for drafting a company's terms of service or privacy policy - use terms-of-service instead.
The same file is in 1 other repository
SkillMedev/skills/skills/fact-checker Skill
5★ repoVerifies discrete factual claims against multiple independent sources and returns a calibrated verdict - Verified, Likely true, Likely false, Unverifiable, or False - with confidence and citations. Use when someone asks "is this true", "fact-check this claim", "did X really happen", "verify this statistic before we publish", or pastes a quote, number, or viral post to check. Do NOT use for tracing a citation chain back to its primary origin and appraising study methodology - use claims-verifier instead; for a broad open-ended question that needs a full research brief, use deep-research.
The same file is in 1 other repository
SkillMedev/skills/skills/job-application Skill
5★ repoTailors a resume and writes a cover letter for one specific job description - mirroring JD keywords for ATS parsing, reordering bullets by relevance, quantifying impact, and reporting which JD keywords matched and which are missing. Use when someone asks "tailor my resume to this job", "write a cover letter for this posting", "will my resume pass the ATS", or shares a job description alongside their resume. Do NOT use for writing or restructuring a resume without a target job - use resume-writer instead; for critique of an existing resume, use resume-reviewer.
The same file is in 1 other repository
SkillMedev/skills/skills/lead-enrichment Skill
5★ repoTurns a raw or partial prospect list into a send-safe dataset by filling missing fields (work email, direct or mobile phone, title, firmographics, technographics) through a per-field provider waterfall, verifying every email, and stamping freshness. Use when someone says "enrich this list", "find the email for these people", "verify these emails before we send", "what do I do with catch-all domains", "this list is a year old, is it still good", "dedupe and clean this CSV", or "why is my bounce rate spiking". Do NOT use for selecting WHO to target and building the list itself - use prospect-list-builder. Do NOT use for tool-specific credit mechanics and filter syntax - use apollo-prospecting. Pair with cold-email-deliverability for the inbox-protection side of verification.
The same file is in 1 other repository
SkillMedev/skills/skills/literature-review Skill
5★ repoProduces a thematic literature review that organizes a field into an argument - consensus, disputes, evidence quality, and the open gap the reader should care about. Use when someone asks "write my related-work section", "review the literature on X", "what does the research say about X", or "organize these papers into themes". Do NOT use for an exhaustive, protocol-registered review with formal inclusion criteria and risk-of-bias appraisal - use systematic-review instead. Do NOT use for synthesizing interviews or mixed non-academic sources into decision themes - use research-synthesis instead.
The same file is in 1 other repository
SkillMedev/skills/skills/manuscript-reviser Skill
5★ repoUse when revising fiction prose that ALREADY EXISTS - a second/third-draft pass on a chapter or scene, a continuity or POV-consistency check, fixing a scene that drags, cutting dead weight, or tightening overwritten prose at the line level. Do NOT use to draft a brand-new scene from nothing (use Fiction Scene Writer), to build or mimic an author's voice (use Ghostwriter), or for neutral encyclopedic prose (use Wikipedia Style Writer); to outline or re-architect the plot at the beat level, use Story Structure Architect.
The same file is in 1 other repository
SkillMedev/skills/skills/migration-safety-checker Skill
5★ repoRewrite a schema migration into independently deployable, zero-downtime steps that never take a long-held blocking lock on a live table. Use when you are about to run an ALTER TABLE, CREATE INDEX, add a constraint, rename a column, or change a column type against a production database with live traffic. Do NOT use for greenfield table/column design with no rows yet - use database-schema instead; do NOT use for broad correctness/integrity review of a migration - use review-db instead.
The same file is in 1 other repository
SkillMedev/skills/skills/performance-review-writer Skill
5★ repoWrites fair, specific, evidence-based performance reviews and ratings. Use when drafting or preparing for calibration to reduce recency bias and vague praise or criticism.
The same file is in 1 other repository
SkillMedev/skills/skills/regex-master Skill
5★ repoAuthors, debugs, and hardens regular expressions - test-cases-first workflow, flavor-aware construction (JS, PCRE, Python re, RE2), catastrophic-backtracking detection and rewrites, and annotated verbose patterns with a verification table. Use when someone asks "write a regex for X", "why doesn't this regex match", "is this regex safe for user input", "explain what this pattern does", or a validation regex is hanging the server on certain inputs. Do NOT use for parsing HTML, JSON, or CSV - those need real parsers, not patterns - and do NOT use for full input-validation architecture or injection defenses - use secure-code-review instead.
SkillMedev/skills/skills/resume-reviewer Skill
5★ repoCritiques an existing resume against a scored rubric, rewrites the weakest bullets, runs a keyword gap analysis, and exports a .docx review. Use when someone wants honest feedback on a resume they already have.
The same file is in 1 other repository
SkillMedev/skills/skills/review-engine Skill
5★ repoBuilds a systematic review generation and response engine for a local service business - the ask-at-peak-satisfaction timing rule, SMS ask scripts, a review-velocity target benchmarked to the top competitor, and word-for-word response procedures for 1-3 star reviews. Use when an owner asks "how do I get more Google reviews", "a customer left a bad review, what do I say", "should I text customers for reviews", or "why does my competitor have way more reviews". Do NOT use for the rest of the Google Business Profile setup - use google-business-profile-optimizer instead. Do NOT use for turning existing reviews into website FAQ content - use review-to-faq-builder instead.
The same file is in 1 other repository
SkillMedev/skills/skills/review-to-faq-builder Skill
5★ repoMines customer reviews and Q&A exports into a pre-purchase PDP FAQ and objection-handling block that answers shopper hesitation before it forms, ordered by conversion impact. Use when someone asks "turn these reviews into an FAQ", "shoppers keep asking the same questions before buying", "how do I address the negative reviews on the product page", or has a review or Q&A export and wants to write or rebuild a product page FAQ or cut returns from preventable surprises. Do NOT use to analyze support tickets or CSAT/NPS verbatims for quality root causes - use csat-root-cause instead; do NOT use to write the main product description - use product-description-writer instead.
The same file is in 1 other repository
SkillMedev/skills/skills/secure-code-review Skill
5★ repoReviews code for the security flaw classes that cause the most breaches - broken authorization and IDOR, injection, SSRF, mass assignment, and unsafe deserialization - and returns a short, focused findings list with concrete fixes. Use when someone asks "review this code for security issues", "is this endpoint safe", "check this PR for vulnerabilities", or is shipping auth logic, new API endpoints, file handling, or anything that touches untrusted input. Do NOT use for general code quality, style, or maintainability review - use code-review-checklist instead; for prioritizing findings a scanner already produced, use vulnerability-triage; for design-stage analysis before code exists, use threat-model-stride.
The same file is in 1 other repository
SkillMedev/skills/skills/social-video-formatter Skill
5★ repoReframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compose / remotion-render to author and export.
The same file is in 1 other repository
SkillMedev/skills/skills/systematic-review Skill
5★ repoRuns a PRISMA-compliant systematic review from PICO question and pre-registered protocol through search strings, two-stage screening, risk-of-bias appraisal, and GRADE-rated synthesis. Use when someone asks "run a systematic review", "build my search strategy and inclusion criteria", "screen these studies against a protocol", or "meta-analyze the evidence on X". Do NOT use for a thematic narrative review of a field without a registered protocol and exhaustive search - use literature-review instead. Do NOT use for synthesizing mixed non-study sources into decision themes - use research-synthesis instead.
The same file is in 1 other repository
SkillMedev/skills/skills/team-health-check Skill
5★ repoAssesses a team's health across three independent dimensions - delivery, morale, and clarity - using observable signals from the last 8 weeks, then maps each red or yellow signal to one manager action with a 2-week horizon. Use when a manager asks "is my team okay", "how do I tell if morale is slipping", "we keep missing sprints and I don't know why", or wants a quarterly team health review. Do NOT use for facilitating a single sprint retrospective - use sprint-retro-facilitator instead - for structuring individual 1:1s - use 1on1-agenda - or for defining how a new team works together - use team-charter instead.
The same file is in 1 other repository
SkillMedev/skills/skills/vercel-firewall-and-botid Skill
5★ repoHarden a Vercel app at the platform edge - the Vercel WAF (custom rules, IP blocking, managed rulesets like OWASP CRS + bot_protection + ai_bots, rate limiting), Attack Challenge Mode, system bypass rules, automatic DDoS mitigation, and BotID bot verification on sensitive routes. Use when someone says "protect my Vercel app", "add a WAF rule", "rate limit my API", "block this IP / country / user-agent", "I'm getting DDoSed", "stop bots / scrapers / AI crawlers", "turn on Attack Mode", "verify human vs bot on checkout/signup/login", or "set up BotID". Do NOT use for app-level auth/session logic - that is application code; do NOT use for env vars or secrets - use vercel-env-management; do NOT use for the deploy/promote/rollback flow - use vercel-deploy-pipeline.
The same file is in 1 other repository
SkillMedev/skills/skills/visual-hierarchy Skill
5★ repoDiagnoses and fixes visual hierarchy in a page, screen, or layout using ranked levers - size, weight, color, position, whitespace - and the one-focal-point-per-view rule. Use when someone asks "why does this layout feel flat", "what should the eye see first", "everything is competing on this screen", or wants the reading order of a composition made intentional. Do NOT use for a full multi-dimension design review covering usability and craft - use design-critique instead; for building the underlying type scale, use typography-system.
The same file is in 1 other repository
SkillMedev/skills/skills/weekly-review Skill
5★ repoRuns a timeboxed weekly review - empty every inbox to a decision, audit every open commitment, and pick the 3-5 outcomes that define next week. Use when someone asks "walk me through a weekly review", "help me plan my week", "my task system feels stale and I don't trust it", or "I keep dropping commitments". Do NOT use for setting up the underlying capture-and-organize system itself - use gtd-system instead - or for tracking long-horizon personal goals with an accountability loop - use goals-accountability instead.
The same file is in 1 other repository
Sudhakaran88/solopreneur-skills/skills/saas-landing-page Skill
5★ repoWhen the user wants to audit, teardown, score, or improve a SaaS homepage or landing page. Use when the user says "review my SaaS landing page," "why isn't my homepage converting," "landing page teardown," "SaaS homepage audit," "homepage critique," "improve my hero section," or "landing page CRO for SaaS." Scores on 10 conversion criteria and rewrites weak copy.
zapgun-ai/clawback/.skills/verify-config Skill
no license5★ repoConfig doctor for clawback — loads the merged config (DEFAULTS < global < ./CLAWBACK.md < CLI overrides) exactly as the proxy's loadConfig does, prints a secret-free summary of the resolved values plus the merge-order sources, and exits non-zero if the canonical CLAWBACK.md did NOT take effect (host not 0.0.0.0, tls off, or adminToken missing) so a bad parse fails loudly instead of silently falling back to loopback defaults. Read-only; never prints the adminToken value, only its length. Use to confirm a CLAWBACK.md edit actually parsed and merged before starting the proxy, or to debug which config layer won.
HsuanYuLee/polaris/.claude/skills/check-pr-approvals Skill
5★ repo掃描使用者的 open PR,偵測 CI 狀態、未回覆 review comments、approval 數量,分類為三種狀態(可催/需修/已達標)後由使用者選擇催 review 或手動修正。Trigger: '我的 PR', 'check PR approvals', 'PR 狀態', '催 review', '催 PR', 'PR 被 approve 了嗎', '幫我掃我的 PR', '請同仁 review', '請同仁幫我 review', '請大家 review', '請大家幫我 review', '請大家幫忙看一下', '找人 review', '找誰 review', '請[人名/角色]幫我 review', '請[人名/角色]幫忙看 PR'. 主語為同仁/大家/人名/角色的「請X幫我 review」屬於催 review 範疇,不要 route 到 review-pr。
HsuanYuLee/polaris/.claude/skills/engineering Skill
5★ repoEngineer-minded execution orchestrator: takes a planned JIRA ticket and implements it with strict quality discipline — TDD, lint, typecheck, test, behavioral verify, PR. Two modes: first-cut (new implementation) and revision (fix PR review comments by returning to the work order). Local-only workflows may register delivery extensions, but those extensions are not part of the portable skill contract. Supports batch mode via parallel sub-agents. Trigger: "做 PROJ-123", "work on", "engineering", "開始做", "接這張", "做這張", "修 PROJ-123", "fix review on PROJ-123", PR URL (from pr-pickup or direct), or user provides JIRA ticket key(s). NOT for planning: Bug → refinement Bug source mode first; Story/Task/Epic → breakdown first. Key distinction: "下一步" / "繼續" without ticket key → my-triage (zero-input router + resume scan).
HsuanYuLee/polaris/.claude/skills/review-inbox Skill
5★ repoUse when the user wants to discover and review PRs across the team awaiting their attention. NOT for a single specific PR (use review-pr). Supports three discovery modes: Label (GitHub label scan), Slack (channel-wide scan), Thread (specific Slack thread URL). Trigger: '掃 PR', 'review 大家的 PR', '批次 review', '有哪些 PR 要我看', Slack thread URL + review intent ('review <slack_url>', '幫我看這串'). Key: '我的 PR' → check-pr-approvals; '大家的 PR' / Slack URL → here; single PR URL → review-pr.
HsuanYuLee/polaris/.claude/skills/review-pr Skill
5★ repoReview someone else's PR as a code reviewer: read the PR diff, check against .claude/rules, leave inline comments on issues found, and submit a review with APPROVE or REQUEST_CHANGES. Use when the user asks the assistant to review a PR (subject omitted or = self), e.g.: "review PR", "review 這個 PR", "review 此 PR", "review 該 PR", "幫我 review 這個 PR" (without team subject), "review for me", "code review", or shares a PR URL with self-directed review intent. NOT for "請<同仁/大家/人名>幫我 review" (subject = others) — that is 催 review, route to check-pr-approvals. NOT for "review 大家的 PR" / "掃 PR" (object = others' PRs) — route to review-inbox. NOT for fixing review comments on your own PR — route to engineering revision mode. (use engineering revision mode for that).
HsuanYuLee/polaris/.claude/skills/sasd-review Skill
5★ repoGenerates a SA/SD (System Analysis / System Design) document for a JIRA ticket — a structured implementation plan produced before coding begins. Use this skill whenever the user mentions SASD, SA/SD, 寫 SA, 出 SA/SD, SA 文件, SD 文件, 架構文件, implementation plan, 系統分析, 系統設計, 技術設計, 異動範圍, dev scope, design doc, technical design, or asks to analyze what changes are needed for a ticket, plan the implementation approach, or produce a technical design document — even if they don't explicitly say "SA/SD".
HsuanYuLee/polaris/.claude/skills/verify-AC Skill
5★ repoQA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUAL_REQUIRED/UNCERTAIN, and presents observed vs expected as pure facts (no root-cause judgement). On FAIL, surfaces human disposition gate (spec issue vs implementation drift); on PASS, it may transition the AC ticket to Done only after verification artifact/report is current and the shared verification contract resolves to PASS. Trigger: "驗 PROJ-123", "verify {TICKET}", "verify AC", "跑驗收", "AC 驗證". NOT for planning or implementation: implementation drift routes to refinement Bug source mode; spec issue routes back to refinement.
HsuanYuLee/polaris/.claude/skills/visual-regression Skill
5★ repoTransitional standalone visual regression guard using before/after screenshot comparison. Two modes: SIT (compare staging vs local dev) or Local (compare git-stashed base vs current changes). No long-lived baselines — captures fresh screenshots each run and deletes after comparison. Config-driven from workspace-config.yaml. Use when: "跑 visual regression", "檢查畫面", "頁面有沒有壞", "visual test", "screenshot test", "畫面測試", "截圖比對", "有沒有跑版", "畫面壞了嗎", "UI 有沒有問題", "check if pages look right", for standalone manual investigation. Engineering / verify-AC Layer C uses scripts/run-visual-snapshot.sh instead.
shortcuts/radin/skills/radin-review Skill
5★ repoRun a thermo-nuclear code quality review over a scope (commit, PR, directory, or a range like "since yesterday") and log each finding as a BACKLOG.md entry instead of printing to terminal. Use for /radin-review, "review and log to backlog", "audit this commit/PR/directory and file backlog entries", "turn this review into a backlog".
ramboz/jig/hosts/claude/skills/arch-review Skill
5★ repoTeam baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).
ramboz/jig/hosts/claude/skills/code-health Skill
5★ repoRun a static-analysis pass on a project — detect the ecosystem (Python or Node), drive its linter (ruff / eslint, plus advisory pyright/complexity/ prettier and a cross-ecosystem duplication signal) via the `health.py` helper, and act on the normalized exit code (0 clean / 1 findings / 2 no-linter). Auto-triggers when you say lint this, check code health, run the linter, ask is this code clean, ask any lint issues, or want a static analysis pass. Tools are resolved on PATH or run ephemerally via uvx / pipx / npx — it installs nothing. Defers to any other installed skill whose description identifies it as handling linting, static analysis, or code quality — prefer it over this baseline. Do not use for running tests (use `/jig:tdd-loop`), for security review (use `/jig:security-review`), for spec-compliance review of a finished slice (use `/jig:independent-review`), or for general PR craft review (use `/jig:pr-review`).
ramboz/jig/hosts/claude/skills/independent-review Skill
5★ repoBuild the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without access to the implementation conversation. Use after an implementer subagent completes a spec slice (when the slice is ready for REVIEWED), or after a deviation log is written (for reconciliation review). Do not use for ad-hoc code review unrelated to a spec, or for reviewing a spec's authorship (that's the READY_FOR_REVIEW step in spec-workflow).
ramboz/jig/hosts/claude/skills/pr-review Skill
5★ repoTeam baseline for PR and code review — produces scope, blockers, nits, and strengths. Auto-triggers when you say review this PR, check this diff, review these changes, pre-review before I share, what do you think of this PR, or review the diff on this branch. Defers to any other installed skill whose description identifies it as handling PR review, code review, or diff review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: spec-compliance review of a finished slice (use `/jig:independent-review` instead); standalone architecture-doc review (use `/jig:arch-review`, or a richer installed arch-review skill, instead); single-line typo fixes or trivial whitespace changes (just merge and move on).
ramboz/jig/hosts/claude/skills/security-review Skill
5★ repoTeam baseline for security review — a best-effort heuristic security pass over a diff or change-set. Auto-triggers for review this for security, any vulnerabilities here, security pass on this diff, is this code secure, check this for security issues, or security review this. Uses installed scanners when available; installs nothing. Defers to any other installed skill whose description identifies it as handling security review, SAST, or vulnerability analysis, including `adobe-security-*`; prefer it over this slim baseline. Do not use for spec-compliance review (use `/jig:independent-review`), general PR craft (use `/jig:pr-review`), or secret prevention (`jig-secret-scan`).
ramboz/jig/hosts/codex/plugins/jig/skills/analyze Skill
5★ repoCross-artifact consistency report for jig specs — a non-destructive six-category audit at CRITICAL/HIGH/MEDIUM/LOW severity, covering duplication, ambiguity, underspecification, principle violations, coverage gaps, and terminology drift. Auto-triggers when you say analyze this spec, check for inconsistencies, audit ADR vs spec drift, check whether the decision records still agree with the spec, cross-artifact alignment, find drift in this spec, or audit this spec for principle violations. Do not use for: pre-DRAFT ambiguity scanning (use `/jig:clarify` instead); structural frontmatter or slice-numbering validation (use `spec_lint.py` instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead).
ramboz/jig/hosts/codex/plugins/jig/skills/arch-review Skill
5★ repoTeam baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).
ramboz/jig/hosts/codex/plugins/jig/skills/code-health Skill
5★ repoRun a static-analysis pass on a project — detect the ecosystem (Python or Node), drive its linter (ruff / eslint, plus advisory pyright/complexity/ prettier and a cross-ecosystem duplication signal) via the `health.py` helper, and act on the normalized exit code (0 clean / 1 findings / 2 no-linter). Auto-triggers when you say lint this, check code health, run the linter, ask is this code clean, ask any lint issues, or want a static analysis pass. Tools are resolved on PATH or run ephemerally via uvx / pipx / npx — it installs nothing. Defers to any other installed skill whose description identifies it as handling linting, static analysis, or code quality — prefer it over this baseline. Do not use for running tests (use `/jig:tdd-loop`), for security review (use `/jig:security-review`), for spec-compliance review of a finished slice (use `/jig:independent-review`), or for general PR craft review (use `/jig:pr-review`).
ramboz/jig/hosts/codex/plugins/jig/skills/independent-review Skill
5★ repoBuild the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without access to the implementation conversation. Use after an implementer subagent completes a spec slice (when the slice is ready for REVIEWED), or after a deviation log is written (for reconciliation review). Do not use for ad-hoc code review unrelated to a spec, or for reviewing a spec's authorship (that's the READY_FOR_REVIEW step in spec-workflow).
ramboz/jig/hosts/codex/plugins/jig/skills/pr-review Skill
5★ repoTeam baseline for PR and code review — produces scope, blockers, nits, and strengths. Auto-triggers when you say review this PR, check this diff, review these changes, pre-review before I share, what do you think of this PR, or review the diff on this branch. Defers to any other installed skill whose description identifies it as handling PR review, code review, or diff review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: spec-compliance review of a finished slice (use `/jig:independent-review` instead); standalone architecture-doc review (use `/jig:arch-review`, or a richer installed arch-review skill, instead); single-line typo fixes or trivial whitespace changes (just merge and move on).
ramboz/jig/hosts/codex/plugins/jig/skills/security-review Skill
5★ repoTeam baseline for security review — a best-effort heuristic security pass over a diff or change-set. Auto-triggers for review this for security, any vulnerabilities here, security pass on this diff, is this code secure, check this for security issues, or security review this. Uses installed scanners when available; installs nothing. Defers to any other installed skill whose description identifies it as handling security review, SAST, or vulnerability analysis, including `adobe-security-*`; prefer it over this slim baseline. Do not use for spec-compliance review (use `/jig:independent-review`), general PR craft (use `/jig:pr-review`), or secret prevention (`jig-secret-scan`).
ramboz/jig/skills/analyze Skill
5★ repoCross-artifact consistency report for jig specs — a non-destructive six-category audit at CRITICAL/HIGH/MEDIUM/LOW severity, covering duplication, ambiguity, underspecification, principle violations, coverage gaps, and terminology drift. Auto-triggers when you say analyze this spec, check for inconsistencies, audit ADR vs spec drift, check whether the decision records still agree with the spec, cross-artifact alignment, find drift in this spec, or audit this spec for principle violations. Do not use for: pre-DRAFT ambiguity scanning (use `/jig:clarify` instead); structural frontmatter or slice-numbering validation (use `spec_lint.py` instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead).
ramboz/jig/skills/arch-review Skill
5★ repoTeam baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to any other installed skill whose description identifies it as handling architecture review, design review, RFC review, or technical-design review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: PR/diff review (use `/jig:pr-review` or a richer user-installed PR-review skill instead); spec-compliance review of a finished slice (use `/jig:independent-review` instead); ADR authorship or scaffolding (use `/jig:adr-workflow` — this skill *reviews* an ADR draft; it does not create one).
ramboz/jig/skills/code-health Skill
5★ repoRun a static-analysis pass on a project — detect the ecosystem (Python or Node), drive its linter (ruff / eslint, plus advisory pyright/complexity/ prettier and a cross-ecosystem duplication signal) via the `health.py` helper, and act on the normalized exit code (0 clean / 1 findings / 2 no-linter). Auto-triggers when you say lint this, check code health, run the linter, ask is this code clean, ask any lint issues, or want a static analysis pass. Tools are resolved on PATH or run ephemerally via uvx / pipx / npx — it installs nothing. Defers to any other installed skill whose description identifies it as handling linting, static analysis, or code quality — prefer it over this baseline. Do not use for running tests (use `/jig:tdd-loop`), for security review (use `/jig:security-review`), for spec-compliance review of a finished slice (use `/jig:independent-review`), or for general PR craft review (use `/jig:pr-review`).
ramboz/jig/skills/independent-review Skill
5★ repoBuild the standardized prompt for a fresh reviewer subagent that evaluates implemented work against its spec without access to the implementation conversation. Use after an implementer subagent completes a spec slice (when the slice is ready for REVIEWED), or after a deviation log is written (for reconciliation review). Do not use for ad-hoc code review unrelated to a spec, or for reviewing a spec's authorship (that's the READY_FOR_REVIEW step in spec-workflow).
ramboz/jig/skills/pr-review Skill
5★ repoTeam baseline for PR and code review — produces scope, blockers, nits, and strengths. Auto-triggers when you say review this PR, check this diff, review these changes, pre-review before I share, what do you think of this PR, or review the diff on this branch. Defers to any other installed skill whose description identifies it as handling PR review, code review, or diff review — if such a skill is present, prefer it over this one (jig's version is a slim baseline). Does not defer to the generic built-in `review` skill. Do not use for: spec-compliance review of a finished slice (use `/jig:independent-review` instead); standalone architecture-doc review (use `/jig:arch-review`, or a richer installed arch-review skill, instead); single-line typo fixes or trivial whitespace changes (just merge and move on).
ramboz/jig/skills/security-review Skill
5★ repoTeam baseline for security review — a best-effort heuristic security pass over a diff or change-set. Auto-triggers for review this for security, any vulnerabilities here, security pass on this diff, is this code secure, check this for security issues, or security review this. Uses installed scanners when available; installs nothing. Defers to any other installed skill whose description identifies it as handling security review, SAST, or vulnerability analysis, including `adobe-security-*`; prefer it over this slim baseline. Do not use for spec-compliance review (use `/jig:independent-review`), general PR craft (use `/jig:pr-review`), or secret prevention (`jig-secret-scan`).