Apply hash-verified refactoring edit plans: a weavatrix-refactor-js plan producer computes and proves a plan against the read-only core, then applyeditplan previews it (issuing a confirm token), applies with automatic rollback, and verifiedchange proves it. The only Weavatrix component that writes code.
Detect breaking changes in OpenAPI specs. Use when reviewing API changes, validating PRs that modify API specs, checking backward compatibility, or linting OpenAPI spec quality. Provides diff, lint, and CI check tools.
Monitor conversation to detect user preference statements, save them to disk, review saved preferences, and apply learned rules in every future session.
Review the current Kelos branch, or an explicitly specified PR, issue, or diff, for Kubernetes API and CRD design quality. Use when asked for a Kelos API review, CRD/API compatibility review, Kubernetes API convention review, or review of changes under api/, generated CRDs, examples/, or self-development/ manifests.…
★not rated 0 3d agoASocket: passSnyk: warn87 tokens
Use when the user asks "what changed", "what breaks if I touch X", "what is the blast radius / change impact", "what should I re-verify before claiming done", "show the timeline / churn for this entity", or when working in a project that uses warpline for temporal change-impact tracking. warpline is the Weft…
Review a software delivery milestone from GitHub Issue, PR, Commit, Diff, Review, and Check evidence; enrich risks with cited internal knowledge and matched human experts; then generate synchronized technical-lead and customer-project-manager reports. Use for ShopFlow delivery status, release-risk reviews, scheduled…
Review code or a skill bundle for the patterns that leak credentials and for least-privilege violations. This is a reasoning skill: it sharpens the agent's eye, and it needs no capabilities of its own.
★not rated 0 3mo agoA✓ AI review0 tokens
originalApache-2.0
Audit and optimize a local repository to prepare it for public open-source distribution. Use when the user wants to publish the codebase, cleanup before open-sourcing, review for community standards, sanitize paths and secrets, or when triggers include "clean up repo", "preparar repo", "publico", "open source"…
Governs API-contract changes before they ship. Use when about to merge, deploy, publish, or register/expose agent tools AND the change touches a contract artifact (OpenAPI/Swagger, GraphQL SDL, gRPC/protobuf, AsyncAPI, MCP manifest, or agent tool schemas): get a decision (ALLOW/WARN/REQUIREAPPROVAL/BLOCK) with a risk…
Multi-model deliberation protocol and fast external task offloading (DeepSeek & OpenAI) via MCP. Use for architectural trade-offs, adversarial code review, small task delegation, and fast context reading.
Review code changes using LLMs (Copilot, Ollama, or other providers). Use when asked to review code, diffs, PRs, or when completing a feature and wanting a second opinion.
Use when completing tasks, implementing major features, or before merging — routes code review to the appropriate specialist lens (STRIDE, OWASP, ATAM, TEMPORAL, CPT, MIGRATION, PRIVACY/SECRETS) based on detected signals, with Independent Judge for Tier 3.
A code-review check for function and variable names in the current Git changes. It compares Python, JavaScript, and TypeScript names with the repository's stated naming rules.
Use when Codex must directly operate or troubleshoot the installed grok-plugin-codex MCP capability surface, including CLI/model checks, literal prompt runs or continuations, session inspection or export, and known background-job control. Do not use for bounded repository delegation, implementation, review…
Use when Claude Science must obtain an independent OpenAI Codex review, second opinion, reproducibility check, statistical or figure audit, debugging handoff, or delegated implementation.
Ask the locally authenticated Grok Build CLI for a bounded second opinion from Codex. Use when the user explicitly asks for Grok, wants cross-model comparison, requests a second opinion, or would materially benefit from an independent review of a supplied plan, answer, or diff.
Review a code change for security, standards, production-readiness, and sustainability issues against a governed rule corpus, citing the rule ID and verbatim evidence for each finding. Use when reviewing, hardening, or pre-flighting code before it merges — especially AI-generated code.
Use when reviewing a code change or answering structural questions about a codebase, including definitions, callers, dependencies, routes, affected tests, and history across git revisions. Builds a local Cypher-queryable code graph, uses it alongside the diff and literal search, and verifies every finding against…
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: