Review & quality
19,195 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
apache/magpie/skills/pr-management-code-review Skill
145★ repoWalk a maintainer through deep, sequential code review of open pull requests on the configured `<upstream>` repo. Defaults to the **"my reviews"** queue (the union of five maintainer signals — see the Inputs table); selectors can narrow to a single PR, an area label, or a collaborator subset. Drafts an `approve` / `request-changes` / `comment` review per PR and posts on the maintainer's confirmation.
apache/magpie/skills/pr-management-triage Skill
145★ repoSweep open pull requests on the configured `<upstream>` repo, classify each one against the project's quality criteria, propose a disposition, and — on the maintainer's confirmation — carry out the action via `gh`. Disposition options per PR: draft / comment / close / rebase / CI-rerun / workflow-approve / ping-stale-reviewer / request author confirmation of readiness / mark `ready for maintainer review` / promote bot-authored draft. Does **not** perform code review — that lives in `pr-management-code-review`.
apache/magpie/skills/pre-first-pr-check Skill
145★ repoRun a newcomer-focused pre-flight checklist on a local branch before opening a pull request. Checks CONTRIBUTING conventions, SPDX headers on new files, commit-message shape (including the Generated-by: trailer for AI-assisted work), and the placeholder convention — then returns a structured checklist report. Read-only; no state changes, no PR, no external writes.
apache/magpie/skills/release-verify-rc Skill
145★ repoRead-only pre-flight verification of a staged release candidate (RC) for `<upstream>`. Checks artefact integrity (GPG signatures and checksums), Apache RAT licence headers, NOTICE/LICENSE completeness, prohibited-binary absence (including `.pyc` / `__pycache__`), source-tree integrity (no dangling symlinks or broken internal references), and version-string consistency. Emits a structured PASS / PASS-WITH-WARNINGS / FAIL report. Makes no state change; a `--post-to <planning-issue>` flag proposes a comment for explicit RM confirmation before any posting.
apache/magpie/skills/reviewer-routing Skill
145★ repoGiven an open issue or PR, scores the project's configured reviewer roster across three signals — touched-area eligibility, git-history familiarity with the changed paths, and current open-review load — and proposes a primary reviewer (plus an optional backup). Read-only and propose-then-confirm: nothing is assigned, labelled, or requested without the maintainer's explicit confirmation. An unresolved roster produces an explicit NO ELIGIBLE REVIEWER signal, never a fabricated handle.
apache/magpie/skills/setup-isolated-setup-verify Skill
145★ repoWalk the verification checklist for the framework's secure agent setup and report ✓ done / ✗ missing / ⚠ partial for each check, with concrete evidence (file paths, command output, version strings). Covers nine checks across settings wiring, installed tool versions, and sandbox configuration. Read-only — never modifies anything.
apache/magpie/skills/setup-shared-config-sync Skill
145★ repoCommit + push the user's shared Claude config to the `~/.claude-config` private dotfile-style sync repo. Inspects for uncommitted local edits and unpushed commits, drafts a commit message, and after explicit approval commits and pushes. Runs `git pull --rebase` first if the local checkout is behind, so a push never overwrites concurrent work from another machine. Bootstraps the repo when it is missing: clones the default private remote if it exists, or creates a new private remote + scaffolds the minimal layout if it does not. Never force-pushes; never rewrites already-pushed history; never creates a public remote; never modifies files outside `~/.claude-config/` (except the confirmed fresh-host symlink wiring into `~/.claude/`).
apache/magpie/skills/setup Skill
145★ repoAdopt and maintain the apache-magpie framework in a project repo via the snapshot-based adoption mechanism. The only framework skill committed in an adopter's repo; every other skill is a symlink the adopt sub-action wires up. Sub-actions: `/magpie-setup` - first-time adoption (default; main-checkout only) `/magpie-setup upgrade` - refresh the gitignored snapshot per the committed lock (main-checkout only) `/magpie-setup worktree-init` - symlink a worktree's snapshot to the main's `/magpie-setup verify` - health check + drift detection `/magpie-setup skill-sources` - fetch/pin/symlink skills from trusted external sources listed in the adopter trust list (main-checkout only) `/magpie-setup override <skill>` - open or scaffold an agentic override in `.apache-magpie-overrides/` `/magpie-setup unadopt` - reverse the adoption (snapshot, locks, symlinks, hook, doc sections); preserves `.apache-magpie-overrides/` by default (main-checkout only)
apache/magpie/skills/write-skill Skill
145★ repoAuthor a new skill for the Apache Magpie framework, or update an existing one. Walks the user through the framework's skill shape (frontmatter, resources, placeholder convention, prompt-injection defences, Privacy-LLM gate-check) and validates via the framework's existing [`tools/skill-and-tool-validator`](../../tools/skill-and-tool-validator/). Scaffolds new skills via `init_skill.py`.
arbiterForge/codeArbiter/core/surface/skills/context-check Skill
141★ repoOptional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
The same file is in 2 other repositories
Finishing a development branch
arbiterForge/codeArbiter/core/surface/skills/finishing-a-development-branch Skill
141★ repoThe terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
arbiterForge/codeArbiter/core/surface/skills/release Skill
141★ repoWhen you can't trust yourself with your code base, trust Arbiter.
arbiterForge/codeArbiter/core/surface/skills/tdd Skill
141★ repoWhen you can't trust yourself with your code base, trust Arbiter.
arbiterForge/codeArbiter/core/surface/skills/using-git-worktrees Skill
141★ repoWhen you can't trust yourself with your code base, trust Arbiter.
arbiterForge/codeArbiter/plugins/ca-codex/routines/commit-gate Skill
141★ repoThe only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, commit. Nothing reaches version control without clearing every gate; "it looks good" is not authorization.
arbiterForge/codeArbiter/plugins/ca-codex/routines/context-check Skill
141★ repoOptional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Finishing a development branch
arbiterForge/codeArbiter/plugins/ca-codex/routines/finishing-a-development-branch Skill
141★ repoThe terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
arbiterForge/codeArbiter/plugins/ca-codex/routines/release Skill
141★ repoThe single permitted path to a version tag, for any of the four independently-versioned plugins. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the target plugin as its one argument (default ca), derives the SemVer bump from Conventional-Commits history since that plugin's last tag, rolls the commits into that plugin's CHANGELOG, writes an annotated tag in that plugin's namespace, and on authorization publishes it as a GitHub Release with the changelog section as its notes. A release commit, if needed, routes through commit-gate; the tag and Release are never published without explicit authorization.
arbiterForge/codeArbiter/plugins/ca-codex/routines/tdd Skill
141★ repoThe test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.
arbiterForge/codeArbiter/plugins/ca-codex/routines/using-git-worktrees Skill
141★ repoOPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates each unit back onto the caller's working branch for the caller's single commit-gate + finishing-a-development-branch exit. Never on the default path; it does not bypass a gate or finish per unit.
arbiterForge/codeArbiter/plugins/ca-codex/skills/ca-commit Skill
141★ repoRun the full commit gate — the only sanctioned path to a git commit.
The same file is in 2 other repositories
arbiterForge/codeArbiter/plugins/ca-codex/skills/ca-context-check Skill
141★ repoOptional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
The same file is in 2 other repositories
arbiterForge/codeArbiter/plugins/ca-codex/skills/ca-pr Skill
141★ repoOpen a pull request the only sanctioned way — clear every BLOCK-level review finding, then stage the PR. Never a direct write to the default branch.
arbiterForge/codeArbiter/plugins/ca-codex/skills/ca-review Skill
141★ repoReview a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.
arbiterForge/codeArbiter/plugins/ca-pi/routines/commit-gate Skill
141★ repoThe only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, commit. Nothing reaches version control without clearing every gate; "it looks good" is not authorization.
arbiterForge/codeArbiter/plugins/ca-pi/routines/context-check Skill
141★ repoOptional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Finishing a development branch
arbiterForge/codeArbiter/plugins/ca-pi/routines/finishing-a-development-branch Skill
141★ repoThe terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
arbiterForge/codeArbiter/plugins/ca-pi/routines/release Skill
141★ repoThe single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the SemVer bump from Conventional-Commits history since that target's last tag, rolls the commits into that target's CHANGELOG, writes an annotated tag in that target's namespace, and on authorization publishes it as a GitHub Release with the changelog section as its notes. A release commit, if needed, routes through commit-gate; the tag and Release are never published without explicit authorization.
arbiterForge/codeArbiter/plugins/ca-pi/routines/tdd Skill
141★ repoThe test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.
arbiterForge/codeArbiter/plugins/ca-pi/routines/using-git-worktrees Skill
141★ repoOPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates each unit back onto the caller's working branch for the caller's single commit-gate + finishing-a-development-branch exit. Never on the default path; it does not bypass a gate or finish per unit.
arbiterForge/codeArbiter/plugins/ca-pi/skills/ca-commit Skill
141★ repoRun the full commit gate — the only sanctioned path to a git commit.
arbiterForge/codeArbiter/plugins/ca-pi/skills/ca-context-check Skill
141★ repoOptional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
arbiterForge/codeArbiter/plugins/ca-pi/skills/ca-pr Skill
141★ repoOpen a pull request the only sanctioned way — clear every BLOCK-level review finding, then stage the PR. Never a direct write to the default branch.
arbiterForge/codeArbiter/plugins/ca-pi/skills/ca-review Skill
141★ repoReview a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.
arbiterForge/codeArbiter/plugins/ca/skills/commit-gate Skill
141★ repoThe only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, commit. Nothing reaches version control without clearing every gate; "it looks good" is not authorization.
arbiterForge/codeArbiter/plugins/ca/skills/context-check Skill
141★ repoOptional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Finishing a development branch
arbiterForge/codeArbiter/plugins/ca/skills/finishing-a-development-branch Skill
141★ repoThe terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.
arbiterForge/codeArbiter/plugins/ca/skills/release Skill
141★ repoThe single permitted path to a version tag, for any of the four independently-versioned plugins. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the target plugin as its one argument (default ca), derives the SemVer bump from Conventional-Commits history since that plugin's last tag, rolls the commits into that plugin's CHANGELOG, writes an annotated tag in that plugin's namespace, and on authorization publishes it as a GitHub Release with the changelog section as its notes. A release commit, if needed, routes through commit-gate; the tag and Release are never published without explicit authorization.
arbiterForge/codeArbiter/plugins/ca/skills/tdd Skill
141★ repoThe test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.
arbiterForge/codeArbiter/plugins/ca/skills/using-git-worktrees Skill
141★ repoOPTIONAL per-task isolation for autonomous parallel work. Routed to only on explicit opt-in by subagent-driven-development or dispatching-parallel-agents, so parallel units mutate files without colliding. Stands up one worktree per unit, works it in isolation, then integrates each unit back onto the caller's working branch for the caller's single commit-gate + finishing-a-development-branch exit. Never on the default path; it does not bypass a gate or finish per unit.
Dave-London/Pare/io.github.Dave-London/lint MCP server
141★ repoStructured linting output (ESLint, format-check) as typed JSON diagnostics.
Dave-London/Pare/io.github.Dave-London/pare-git MCP server
141★ repoPare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.
Dave-London/Pare/io.github.Dave-London/pare-lint MCP server
141★ repoPare Lint ג€” Structured linting and formatting (ESLint, Prettier, Biome, Oxlint) as typed JSON.
Dave-London/Pare/io.github.Dave-London/git MCP server
141★ repoStructured git operations (status, log, diff, branch, show) as typed JSON.
Mark393295827/third-brain-v7-skills/skills/startup-evaluation Skill
137★ repoagent wiki +engineering skills
Mark393295827/third-brain-v7-skills/skills/verify-before-claim Skill
137★ repoagent wiki +engineering skills
Mark393295827/third-brain-v7-skills/skills/wiki-lint Skill
137★ repoUse when an Obsidian wiki needs a reproducible health audit for structure, provenance, links, understanding, lifecycle, and promotion readiness.
karaage0703/ai-assistant-workspace/skills/xs-code-reviewer Skill
136★ repo複数のAI(自分/Codex/Grok/Cursor等)でPRをレビューするスキル。GitHub PRの差分を取得し、各AIの視点を統合したレビューを提供する。GitHubへの投稿はユーザーの明示OK後に行う。「PRレビューして」「コードレビューして」「PR#123をチェック」で使用。
harness/harness-skills/skills/enforce-sbom Skill
135★ repoAdd an SBOM Policy Enforcement (SscaEnforcement / CdSscaEnforcement) step to an existing Harness pipeline to verify SBOM attestations and apply OPA SBOM policy sets. Supports CI, Security, and CD (Deployment) including CI-only pipelines — if no Deploy stage exists, add one via Phase 3b (service, environment, infra, containerized step group) then place CdSscaEnforcement before deploy. Supports container images and repositories from Artifact Registry, Third-Party registries (docker, ECR, GCR, GAR, ACR), and Git. Matches Pipeline Studio SBOM Policy Enforcement UI. Only works with existing pipelines (may append a Deploy stage). Use when asked to enforce SBOM policies, add SBOM policy enforcement, verify SBOM attestation in pipeline, or block non-compliant components. Trigger phrases: enforce SBOM, SBOM policy enforcement, SBOM policy step, verify SBOM policy, SscaEnforcement, add policy enforcement after SBOM.
harness/harness-skills/skills/enforce-slsa Skill
135★ repoAdd an SLSA Verification (SlsaVerification) step to an existing Harness pipeline to verify SLSA provenance attestations and optionally enforce OPA policy sets on provenance data. Supports CI and CD (Deployment) including CI-only pipelines — append a Deploy stage via Phase 3b when verifying before deploy. Supports Docker, ECR, GCR, GAR, ACR, HAR, and Local artifacts. Only works with existing pipelines. Use when asked to verify SLSA, enforce SLSA policies, add SLSA verification step, validate SLSA attestation, or gate deploy on SLSA provenance. Trigger phrases: enforce SLSA, SLSA verification, verify SLSA, SLSA policy enforcement, SlsaVerification, verify SLSA attestation, add SLSA verify step.
harness/harness-skills/skills/manage-pull-requests Skill
135★ repoManage Harness Code pull requests via MCP. List, create, update, and merge PRs; add reviewers and submit review decisions (approve / request changes); post, update, and delete comments; read the discussion timeline; and check CI status. Use when asked to open a PR, merge a PR, approve a PR, leave a code review comment, request changes, assign reviewers, or inspect PR checks and activity. Trigger phrases: pull request, PR review, merge PR, approve PR, request changes, add reviewer, PR comments, PR checks, PR activity, code review.
harness/harness-skills/skills/scorecard-review Skill
135★ repoReview service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says "scorecard", "service maturity", "production readiness", "compliance score", or asks about service health scores.
harness/harness-skills/skills/verify-sign Skill
135★ repoAdd an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.
jtrackingai/analytics-tracking-automation/skills/tracking-verify Skill
133★ repoUse when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
jjmartres/opencode/opencode/skills/caveman-review Skill
133★ repoUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
jjmartres/opencode/opencode/skills/worktrunk Skill
133★ repoUse this skill when the user asks about Worktrunk (wt), git worktree management, running parallel AI agents with worktrees, setting up wt hooks, configuring wt.toml, using `wt switch`, `wt list`, `wt merge`, `wt remove`, `wt step`, LLM commit messages, or integrating Worktrunk with your AI agent. Also trigger when the user wants to run multiple AI agent sessions in parallel across isolated git branches, or automate dev server / database / dependency setup per worktree. Always use this skill for any question involving the `wt` CLI, worktree lifecycle automation, or the worktrunk plugin.
The same file is in 1 other repository
elisaterumi-ai/agent-skills-in-practice/examples/commit-message-generator Skill
129★ repoGenerates standardized and meaningful commit messages following best practices. Use when writing or improving commit messages.
elisaterumi-ai/agent-skills-in-practice/examples/pr-review Skill
129★ repoReviews pull requests for code quality, readability, security, and best practices. Use when analyzing code changes or reviewing a PR.
openaccountant/skills/personal/spending-review Skill
127★ repoGenerate a categorized spending breakdown with month-over-month trends.
Investigating repository history
CodeAlive-AI/ai-driven-development/skills/investigating-repository-history Skill
127★ repoInvestigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments, squash/rebase/cherry-pick/rename heuristics, and cited evidence. Use when asking why code exists, whether a change is safe, what PR introduced behavior, or before editing API, compatibility, security, concurrency, persistence, migration, or performance-sensitive code.