Exhaustive adversarial documentation verification. Use when checking README accuracy, API documentation completeness, or any docs where missing features could mislead users. Enumerates ALL features from source, compares to docs, proves coverage gaps with formal logic.
Esta skill transforma al agente en un Ingeniero de QA especializado en Yari Medic. Su misión es auditar código contra los documentos de grounding en data/projectcontext/.
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
A code-review workflow written in Chinese that checks software changes for correctness, security, performance, and maintainability. It also defines a report format for critical issues and suggestions.
Give an animated, narrated "explain like I'm five" tour of a GitHub pull request in the user's browser, driven live through the CodeTour MCP server. Use when the user asks to "tour this PR", wants an "executive tour", "animated walkthrough", or "guided tour" of a pull request, asks to "explain this PR like I'm five"…
Structured code review for bugs, regressions, tests, and standards. Report-only by default; apply fixes only when the current user or upstream caller explicitly requests review-and-fix. mode:agent is always report-only.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Review Bitbucket Server pull requests from the shell with the bb CLI, with no MCP server process involved. Use when the user asks to review a Bitbucket PR, look at a merge request, read a PR's diff or changed files without cloning, post review comments or inline findings, draft a review and publish it with a verdict…
Trigger: PR assessment, zeroslopsubmitassessment, conceptual question, mutation patch, learningAreas. Score a developer then persist via the Zero Slop MCP tool. Not Clerk.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Establish a short, evidence-backed decision gate before architecture or broad implementation when missing facts, requirements, external behavior, or acceptance criteria could change the direction. Use only for consequential or materially uncertain work.
Work with Gerrit code review from the terminal using the gerrit-cli binary - search changes, read diffs and inline comments, draft and publish review comments, add reviewers, set topic or WIP, abandon and revert. Use whenever the user mentions Gerrit, a CL or change number, a Change-Id, a gerrit. URL, a patchset, or…
Before modifying shared code (types, APIs, utilities), find all consumers. Prevents partial migrations and broken integrations. Trigger before changing any exported symbol.
A GitLab workflow tool for GitLab, a service for hosting code and managing team development work. It covers merge requests, code review, automated build checks, branches, and merges while following stated team rules.
Use Claude as an independent second-model reviewer of Codex work. Supports normal and adversarial reviews, exact commit scope, working-tree or branch scope, explicit files, background jobs, wait-for-result delivery, status, result, and cancellation.
Verify multi-repo agent claims at Git HEAD with GitPin (index-free evidence). Use for catalog, search candidates, pin.prove / pin.proveset, pin.verify / pin.verifyset, EvidenceBrief, and citation checks. Never treat dirty worktrees or search hits as claims.
Use stash MCP to work with Bitbucket Server projects, repositories, and pull requests.
★not rated 0 2d agoA19 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: