agentsclimarketplace

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

  • Sendback

    escoffier-labs/skillet/skillet/skills/sendback Skill

    4★ repo

    A skillet full of agent skills that actually ship work. Production-tested SKILL.md workflows for audits, security, releases, and handoffs.

  • Stagiaire

    escoffier-labs/skillet/skillet/skills/stagiaire Skill

    4★ repo

    A skillet full of agent skills that actually ship work. Production-tested SKILL.md workflows for audits, security, releases, and handoffs.

  • Worktree

    escoffier-labs/skillet/skillet/skills/worktree Skill

    4★ repo

    A skillet full of agent skills that actually ship work. Production-tested SKILL.md workflows for audits, security, releases, and handoffs.

  • Conventional commits

    stealth-engine/skills/skills/conventional-commits Skill

    4★ repo

    The Conventional Commits format — also called "semantic commits" / semantic commit messages — a `type(scope): description` header (`feat`, `fix`, …) plus an optional `BREAKING CHANGE` footer, and how it makes history machine-readable to drive automated version bumps and changelogs. Use when writing a commit message or PR title, deciding the type/scope/bump for a change, setting up or fixing a repo's commit convention, making commits parseable by semantic-release / changelog tooling, validating PR titles, or when a release didn't bump or the changelog came out blank because a commit wasn't conventional. Covers the type→semver mapping, breaking changes, scopes, monorepo scopes, and squash-merge PR titles.

  • Dual agent review

    stealth-engine/skills/skills/dual-agent-review Skill

    4★ repo

    Review a change set with two or more independent AI reviewers in parallel — a Sonnet subagent and the CodeRabbit CLI — then merge + dedupe their findings, triage valid vs invalid, fix (directly or via parallel fix-subagents), and hand back a report of what was fixed/how and what was ignored/why. Use when asked to 'review my changes with two/multiple agents', 'dual-agent / multi-reviewer review', 'get a second opinion from Sonnet and CodeRabbit', 'review the diff and fix the valid issues', 'run parallel reviewers and fix in parallel', or to cross-check one reviewer against another before committing. Diff-scoped by default (branch-vs-base or the PR diff), like CodeRabbit — NOT a whole-repo audit.

  • Git trunk branch and pr automation

    stealth-engine/skills/skills/git-trunk-branch-and-pr-automation Skill

    4★ repo

    Trunk-based Git workflow with enforced branch naming and squash-merge PR titles. Use when setting up or standardising a branch/PR workflow, naming branches (feature/ fix/ hotfix/ and AI-agent prefixes claude/ cursor/ codex/ copilot/ codegen-bot/ dependabot/), configuring squash-only merges where the PR title becomes the commit and the body is the concatenated commits, making the PR title a valid Conventional Commit, adding GitHub Actions that validate branch names or auto-normalise PR titles, fixing a PR-title bot that loops, or deciding trunk vs release branches. Covers the GitHub repo settings, the validation/normalisation workflows, and how it feeds semantic-release.

  • Production release gating

    stealth-engine/skills/skills/production-release-gating Skill

    4★ repo

    Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel Ignored Build Step / `ignoreCommand`, promoting to a staging/`production` branch, or triggering a deploy from a published GitHub Release (GKE, self-hosted, dispatchable targets). Covers three named patterns — Release-Triggered Deploy (`on: release`, `types: [published]`), Promotion Branch (staging/`production`, most portable), and Build-Skip Gate (the Vercel `ignoreCommand` script) — when to use which, works with both per-merge and pooled releases, branch-aware previews, and monorepo dependency-release handling.

  • Resolve merge conflicts

    stealth-engine/skills/skills/resolve-merge-conflicts Skill

    4★ repo

    Resolve git merge/rebase conflicts non-destructively — preserving the intent of BOTH sides — and hand off to a human when a conflict can't be resolved safely. Use when a branch or PR has conflicts with its base ('this branch has conflicts that must be resolved', GitHub mergeable=CONFLICTING / mergeStateStatus=DIRTY), when a rebase / merge / cherry-pick / stash / revert stops with conflict markers (<<<<<<< ======= >>>>>>>), when a PR is behind base and needs updating, when syncing a long-lived branch or back-merging a hotfix, or when deciding rebase vs merge. Covers the safe-resolution rules (no blind -X ours/theirs, hunk-by-hunk with diff3, abort/reflog escape hatches, verify-after), the rebase ours/theirs inversion, lockfile/rename/semantic conflicts, and the escalate-when-stuck criteria.

  • Semantic release automation

    stealth-engine/skills/skills/semantic-release-automation Skill

    4★ repo

    Automate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a `.releaserc` / `release` config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making `main` cut a version on merge, generating CHANGELOG.md, publishing to npm or creating a GitHub Release per release, doing per-package releases in a monorepo (per-package tags + paths-filter matrix), pooling commits into a less-frequent release, or fixing a release that didn't fire / a CI loop from the release commit. Covers the single-package and monorepo flavors and the GitHub Actions workflow.

  • Start

    emaballarin/ccplugins/plugins/autoresearch/skills/start Skill

    4★ repo

    Open a new autoresearch experiment loop — dedicated `ar/…` git branch, `./.ar/` state, and a measured baseline noise floor so later gains can be told apart from run-to-run scatter. Invoke ONLY when explicitly asked to start an autoresearch run, open an experiment loop, or `/ar:start` — e.g. "autoresearch this", "start an ar run", "set up a loop to minimise X". Do NOT auto-fire on ordinary optimisation work. "Make this faster", "improve the accuracy", "tune these hyperparameters", "benchmark this", "find the best configuration" are normal requests to handle directly, not loops. Warranted only when many measured iterations under a locked harness are wanted — it creates a git branch and a commit on first use.

  • Stop

    emaballarin/ccplugins/plugins/autoresearch/skills/stop Skill

    4★ repo

    End the current autoresearch run — append a `status:stopped` sentinel to `./.ar/ar.jsonl`, which is also what halts the external `ar-loop.sh` driver. Use for `/ar:stop`, "stop the loop", "halt autoresearch", or "that's enough iterations". Writes the sentinel and the final report, then prints (does not run) the command to return to the original branch. Never reverts or discards work — every kept commit stays on the experiment branch.

  • Figure style

    emaballarin/ccplugins/plugins/ccscience/skills/figure-style Skill

    4★ repo

    Publication-grade figure correctness and legibility rules. Load before drawing any plot and call `apply_figure_style()` — sets a role-mapped font-size ladder, outward ticks, frameless legends, and 300-dpi output. The skill is a checklist, not a house look: data fidelity (claim-titles tested against every row, excluded data never enters summaries), label economy (floor and ceiling), colour threading, chart-choice-by-data-shape, layout, and a render-then-verify QA loop (bbox collision + per-panel perceptual check). Ships helpers: focal_palette, bar_with_points, strip_with_median, end_of_line_labels, panel_letter, set_frame, panel_crops. For multi-panel figures load `figure-composer`; for whole-paper figure arc load `paper-narrative`.

  • Literature review

    emaballarin/ccplugins/plugins/ccscience/skills/literature-review Skill

    4★ repo

    Find, verify, and synthesize STEM literature across every field — from "what's the seminal paper for X" through full multi-source reviews. Treats journal articles, arXiv/preprints, and conference proceedings as first-class; grounds every claim in a retrieved source, never fabricates DOIs, checks for superseded/withdrawn/refuted work, calibrates confidence to evidence strength (including SOTA/reproduction/ablation caveats for CS and ML), and emits a tidy DOI-pinned BibTeX reference list. Pairs with the deep-researcher agent.

  • Paper narrative

    emaballarin/ccplugins/plugins/ccscience/skills/paper-narrative Skill

    4★ repo

    Judge and reshape the STORY a paper's figures tell. Input is the work itself — manuscript (or abstract) + figure deck — no hand-written brief. `derive_paper_brief_task(abstract, captions)` builds the prompt whose JSON is pitch/vision/per-figure-claims; a handling-editor reviewer on the full deck returns hook_verdict (would Fig 1 make me send this for review?), arc (hook→mechanism→evidence→application), figure_moves (panels in the wrong figure), missing_panels (concrete analyses to RUN), kill_list, and boldest_defensible_fig1. Hands per-figure claims to `figure-composer`. Load when writing or revising a paper.

  • Agent supply chain

    MarieLynneBlock/arcanum-artifex/skills/agentic/agent-supply-chain Skill

    no license4★ repo

    Review, generate, and verify supply-chain integrity controls for AI agent tools, plugins, MCP servers, skills, prompts, and custom agents, including SHA-256 manifests, dependency pinning, provenance evidence, promotion gates, and CI verification.

  • Performance review writer

    MarieLynneBlock/arcanum-artifex/skills/analysis/people-management/performance-review-writer Skill

    no license4★ repo

    Draft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice. Analyses your contributions, emails, and meeting history via WorkIQ, then produces honest, impact-focused drafts using the STAR format. USE FOR: write my performance review, draft self-assessment, peer review, 360 feedback, annual review, mid-year review, upward feedback, write review for colleague, performance appraisal.

  • Data validation and schema contracts

    MarieLynneBlock/arcanum-artifex/skills/data-science/data-validation-and-schema-contracts Skill

    no license4★ repo

    [TODO] Define the specific workflow this skill standardises, including default libraries, quality checks, and expected deliverables.

  • Model selections and cross validation

    MarieLynneBlock/arcanum-artifex/skills/data-science/model-selections-and-cross-validation Skill

    no license4★ repo

    [TODO] Define the specific workflow this skill standardises, including default libraries, quality checks, and expected deliverables.

  • Code review

    MarieLynneBlock/arcanum-artifex/skills/development/code-review Skill

    no license4★ repo

    Applies a consistent, language-agnostic review framework to any code change. It evaluates code across five dimensions, produces prioritised findings with inline suggestions, and distinguishes blockers (must fix before merge) from improvements (worth addressing but not blocking).

  • Review and refactor

    MarieLynneBlock/arcanum-artifex/skills/development/code-review/review-and-refactor Skill

    no license4★ repo

    Review and refactor code in your project according to defined instructions

  • Dotnet design pattern review

    MarieLynneBlock/arcanum-artifex/skills/development/dotnet/dotnet-design-pattern-review Skill

    no license4★ repo

    Review the C#/.NET code for design pattern implementation and suggest improvements.

  • Git workflow

    MarieLynneBlock/arcanum-artifex/skills/development/git-workflow Skill

    no license4★ repo

    Covers the full git workflow for a software project: branch naming conventions, commit message authoring (Conventional Commits standard), PR description templates, and merge strategy advice. It produces ready-to-use git artefacts, not generic advice.

  • Commit message storyteller

    MarieLynneBlock/arcanum-artifex/skills/development/git-workflow/commit-message-storyteller Skill

    no license4★ repo

    Analyses git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "generate a commit", "describe my changes", "what should I commit this as", "commit this", "summarise my diff", or "help me commit". Works with git diff output, staged files, or plain descriptions of changes.

  • Git commit

    MarieLynneBlock/arcanum-artifex/skills/development/git-workflow/git-commit Skill

    no license4★ repo

    Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

  • Git flow branch creator

    MarieLynneBlock/arcanum-artifex/skills/development/git-workflow/git-flow-branch-creator Skill

    no license4★ repo

    Intelligent Git Flow branch creator that analyses git status/diff and creates appropriate branches following the nvie Git Flow branching model.

  • Python pypi package builder

    MarieLynneBlock/arcanum-artifex/skills/development/python/python-pypi-package-builder Skill

    no license4★ repo

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.

  • Sql code review

    MarieLynneBlock/arcanum-artifex/skills/development/sql/sql-code-review Skill

    no license4★ repo

    Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimisation prompt for complete development coverage.

  • Linkedin post formatter

    MarieLynneBlock/arcanum-artifex/skills/documentation/linkedin-post-formatter Skill

    no license4★ repo

    Format and draft compelling LinkedIn posts using Unicode bold/italic styling, visual separators, structured sections, and engagement-optimised patterns. USE FOR: draft LinkedIn post, format text for LinkedIn, create social media post, write thought leadership post, convert content to LinkedIn format, LinkedIn carousel text, Unicode bold italic formatting.

  • Literature review

    MarieLynneBlock/arcanum-artifex/skills/scientific/literature-review Skill

    no license4★ repo

    Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).

  • Peer review

    MarieLynneBlock/arcanum-artifex/skills/scientific/peer-review Skill

    no license4★ repo

    Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.

  • Timesfm forecasting

    MarieLynneBlock/arcanum-artifex/skills/scientific/timesfm-forecasting Skill

    no license4★ repo

    Zero-shot time series forecasting with Google's TimesFM foundation model. Use for any univariate time series (sales, sensors, energy, vitals, weather) without training a custom model. Supports CSV/DataFrame/array inputs with point forecasts and prediction intervals. Includes a preflight system checker script to verify RAM/GPU before first use.

  • Security review

    MarieLynneBlock/arcanum-artifex/skills/security/security-review Skill

    no license4★ repo

    AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.

  • Wireframe reviewer

    yaxeen/storytelling-skills/skills/wireframe-reviewer Skill

    4★ repo

    Use when reviewing or critiquing an existing website wireframe, landing page, or page structure for any niche or business — when you need structured feedback on narrative flow, visual hierarchy, clarity, and conversion path, plus concrete fixes per section. For building a new page structure from scratch, use wireframe-writer.

  • Running review recovery

    danielkinneyspears/federal-proposal-skills/skills/running-review-recovery Skill

    4★ repo

    Runs proposal review recovery for a US Federal bid. Use when the user needs to work color team findings, run recovery after a Pink, Red, or Gold review, assign and track finding closure, verify fixes against Section M and the compliance matrix, or produce a recovery status dashboard. Turns review findings into assigned, completed, and verified corrections before the next milestone.

  • Infra kit.workflow.review

    huyngopt1994/infras-kit/infras-kit-plugin/skills/infra-kit.workflow.review Skill

    no license4★ repo

    Make infra PRs reviewable: PR readiness checklist, traceability to ticket, and how to respond to review feedback.

  • Infra kit.workflow.verify

    huyngopt1994/infras-kit/infras-kit-plugin/skills/infra-kit.workflow.verify Skill

    no license4★ repo

    Standardize post-change verification and “definition of done” evidence for infra work (IaC/Helm/GitHub/Kubernetes).

  • Development contract process

    n-n-code/n-n-code-skills/.agents/skills/development-contract-process Skill

    4★ repo

    Portable workflow for repos that require tracked change contracts, verifier evidence, and smallest-proof validation. Use when a repo has a contract policy file or enforced feature-plan checker.

  • Development contract repo overlay template

    n-n-code/n-n-code-skills/.agents/skills/development-contract-repo-overlay-template Skill

    4★ repo

    Template for authoring or revising the thin repo-local overlay generated by the development contract system. Use when writing overlay guidance that names a target repo's policy path, plan directory, checker command, lifecycle helper, or validation profiles; use `development-contract-process` for ordinary work in a repo that already has the system.

  • Wiki lint

    Misaka16384/Wikify/skills/wiki_lint Skill

    no license4★ repo

    Statically check and repair double-bracket linkages and frontmatter within your compiled wiki directory.

  • Doccraft queue audit

    alexpialetski/doccraft/.claude/skills/doccraft-queue-audit Skill

    4★ repo

    Reconcile the dependency graph, pick-next queue, and backlog status across docs/stories/, docs/queue.md, and docs/backlog.md. Use after adding or editing a story (especially one with depends_on), after reshuffling priorities, or when the user asks "what can I work on next", "what's unblocked", "sanity-check the queue", "check my story dependencies", "fix the queue order", or "what parallel work is ready". In Agent mode (the tool can write files), apply objective mechanical fixes in the same turn and report what changed; in Ask / read-only mode, emit a proposal instead. Stop and report — never guess — on directed cycles, unknown depends_on ids, duplicate ids, or ambiguous editorial reorders.

  • Doccraft queue audit

    alexpialetski/doccraft/templates/skills/doccraft-queue-audit Skill

    4★ repo

    Reconcile the dependency graph, pick-next queue, and backlog status across {{DOCS_DIR}}/stories/, {{DOCS_DIR}}/queue.md, and {{DOCS_DIR}}/backlog.md. Use after adding or editing a story (especially one with depends_on), after reshuffling priorities, or when the user asks "what can I work on next", "what's unblocked", "sanity-check the queue", "check my story dependencies", "fix the queue order", or "what parallel work is ready". In Agent mode (the tool can write files), apply objective mechanical fixes in the same turn and report what changed; in Ask / read-only mode, emit a proposal instead. Stop and report — never guess — on directed cycles, unknown depends_on ids, duplicate ids, or ambiguous editorial reorders.

  • Verify content

    Amalia6767/curator-skills/skills/verify-content Skill

    4★ repo

    Verify AI-generated content against original source materials to detect hallucinations, fabrications, and inaccuracies. Use when the user says "验证", "verify", "核实", "检查幻觉", or asks to check if generated content is accurate.

  • Role reviewer

    BechsteinDigital/claude-shiploop/role-reviewer Skill

    4★ repo

    Use when a completed work package or a bounded diff needs checking — architecture, risks, test quality, truth of DONE/status claims — including as a review subagent in autonomous-loop. Not for whole-repo state audits (→ role-auditor).

  • Postkit review

    Trystan-SA/postkit/templates/project/.claude/skills/postkit-review Skill

    4★ repo

    Critique a draft post against the brand profile (memory/brand_*.md) and theme.css across three lenses — strategy (hook, angle, value arc), copy (CTA, word economy, tone), and design (layout, density, rhythm, typography). Returns HIGH/MEDIUM/LOW findings. Use when the user asks to review, critique, polish, or improve a draft before rendering.

  • Secrets scanner

    roodlicht/accans-sec-skills/skills/secrets-scanner Skill

    no license4★ repo

    Detect and remediate leaked credentials in code and git-history — entropy/regex scanning with gitleaks/trufflehog/detect-secrets, rotate-first incident response, and pre-commit/CI gating to prevent reoccurrence.

  • Security review

    roodlicht/accans-sec-skills/skills/security-review Skill

    no license4★ repo

    Security review workflow for a PR, feature or codebase — scope, automated scans, manual OWASP/CWE pattern-check, prioritize and report. Uses secure-coding as pattern library.

  • Verification loop

    roodlicht/accans-sec-skills/skills/verification-loop Skill

    no license4★ repo

    Structured red-team pass over your own output — surface assumptions, gaps, failure modes and security red flags before shipping.

  • Ieee response

    TenWalk/ieee-skills/ieee-skills-claude/skills/ieee-response Skill

    4★ repo

    Draft the two letters an IEEE submission needs — the point-by-point response to reviewers and the cover letter to the editor — so every comment is answered, every change is traceable to the revised manuscript, and the tone stays cooperative without conceding more than the evidence requires. Use this whenever the user is replying to a review or submitting a manuscript: "respond to reviewers", "rebuttal letter", "reviewer 2 says...", "write a cover letter", "我要回复审稿意见", "审稿回复", "投稿信", "怎么回复 reviewer". For changing the manuscript text the response promises, hand to ieee-writing/ieee-polishing; for new simulations a reviewer demands, hand to ieee-experiments.

  • Ieee response

    TenWalk/ieee-skills/ieee-skills-codex/skills/ieee-response Skill

    4★ repo

    Draft the two letters an IEEE submission needs — the point-by-point response to reviewers and the cover letter to the editor — so every comment is answered, every change is traceable to the revised manuscript, and the tone stays cooperative without conceding more than the evidence requires. Use this whenever the user is replying to a review or submitting a manuscript: "respond to reviewers", "rebuttal letter", "reviewer 2 says...", "write a cover letter", "我要回复审稿意见", "审稿回复", "投稿信", "怎么回复 reviewer". For changing the manuscript text the response promises, hand to ieee-writing/ieee-polishing; for new simulations a reviewer demands, hand to ieee-experiments.

  • Git conventions

    sefaertunc/Worclaude/.claude/skills/git-conventions Skill

    4★ repo

    Branch naming, commit message format, PR workflow, worktree conventions, versioning policy

  • Review and handoff

    sefaertunc/Worclaude/.claude/skills/review-and-handoff Skill

    4★ repo

    Session ending protocol, HANDOFF document format, seamless continuation between sessions

  • Verification

    sefaertunc/Worclaude/.claude/skills/verification Skill

    4★ repo

    Domain-specific verification beyond tests, closing the feedback loop for web, API, CLI, data

  • Review post

    warpirate/linkedin-maxxing/plugins/linkedin-maxxing/skills/review-post Skill

    no license4★ repo

    Use when one of user's already-published LinkedIn posts notably outperformed or underperformed their median, they want to understand a single post in depth before writing a follow-up, or learn from a specific recent post. Trigger phrases include "review this post," "why did this post flop," "why did this post do so well," "what should I do differently next time," "do a postmortem on this post." Per-post counterpart to analyze-performance.

  • Commit

    kborovik/pilot-skills/pilot-plan/skills/commit Skill

    no license4★ repo

    Commit staged git changes w/ descriptive Conventional Commits message. Triggers when user asks to commit, save changes, or mentions GitHub commits. Phrasings: "commit", "save my changes", "commit this".

  • Merge

    kborovik/pilot-skills/pilot-plan/skills/merge Skill

    no license4★ repo

    Merge GitHub PR into main w/ release-ready commit message. Triggers when user mentions merging PR, landing branch, shipping GitHub PR. Phrasings: "merge this", "land the PR", "merge PR #N".

  • Check

    kborovik/pilot-skills/pilot-spec/skills/check Skill

    no license4★ repo

    Read-only drift detector. Diffs SPEC.md vs current code and reports violations grouped by severity. not writes — suggests remedies via spec or build skills, not invokes them. Triggers when user asks to check drift, audit spec, verify invariants, or ask if code still matches invariants. Phrasings: "check drift", "audit the spec", "does the code still match invariants", "check invariants", "spec vs code", "is the spec still accurate?", "did the code drift?".

  • Local lint test

    mpagot/os-autoinst-distri-opensuse-skills/skills/local-lint-test Skill

    no license4★ repo

    Recommends the fastest local commands to validate edited OSADO code before pushing. Activate when the user asks "how do I check my code", "what should I run locally", "lint my changes", "does this compile", "run perltidy", "run perlcritic", "run a unit test", "check formatting", or after editing files to verify correctness. Covers compilation, formatting, linting, unit tests, YAML validation, and static analysis -- always preferring the lightest targeted command over full-suite runs.

  • Vr planner

    mpagot/os-autoinst-distri-opensuse-skills/skills/vr-planner Skill

    no license4★ repo

    Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML schedules, and openqa-clone-job commands.

  • Api design review

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/engineering/skills/api-design-review Skill

    4★ repo

    Review an API contract (REST or GraphQL) before or while it is implemented, checking resource naming, HTTP semantics, status codes, error shape, pagination, versioning, idempotency, and backward compatibility, and producing concrete revisions rather than abstract advice. Use when designing new endpoints, changing an existing API's surface, or reviewing a PR that adds or modifies API routes.

  • Code review response

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/engineering/skills/code-review-response Skill

    4★ repo

    Process code-review feedback with technical rigour — understand each point, check it against the actual codebase, and respond with reasoning or implementation rather than reflexive agreement. Use when you receive review comments (from a human, the code-reviewer agent, or any reviewer) and are about to act on them, especially if any feedback seems unclear or wrong.