Use this skill to configure and understand the built-in auto-review plugin (wstack-auto-review) that fires automated code review subagents on every code change during a session. Triggers: user says "auto review", "otomatik review", "auto code review", "her değişiklikte review", "/auto-review".
Use this skill when external coding agents (Claude Code, Aider, custom scripts) need to participate in the project's shared WrongStack mailbox, or when a user asks to "expose the mailbox", "let Claude Code read the mailbox", "external agent mailbox", "mailbox bridge", or "HTTP mailbox bridge". Starts a loopback HTTP…
Use this skill when you need a background monitoring agent that watches the fleet, detects anomalies, and can intervene on command. Triggers: user says "shadow", "monitoring agent", "fleet watcher", "hoop command", "spike detection".
Use this skill when the user wants to communicate with WrongStack's shared project mailbox from outside WrongStack — read messages sent by WrongStack agents, send replies, broadcast to all, or stay visible as an online agent. Triggers: user says "check the WrongStack mailbox", "send to WrongStack", "wrongstack mail"…
Use this skill when designing, implementing, or reviewing an HTTP API — endpoints, request and response shapes, errors, pagination, versioning, and authorization. Triggers: user says "API", "endpoint", "REST", "route", "status code", "pagination", "request body", "response shape", "OpenAPI", "versioning"…
Use this skill when analyzing WrongStack session journals to explain what happened in a session — tool usage and failures, token spend and cache efficiency, compactions, delegations, loops, and errors. Triggers: user says "audit", "session analysis", "analyze the session", "log analysis", "why did this session cost so…
Use this skill when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and verify one real defect. Trigger on the explicit vocabulary — "bug", "bug hunt", "/bughunt", "scan for issues", "find problems"…
Use this skill for post-session code quality review of files added or modified during a WrongStack session. It runs automatically when a session ends, and on demand. Trigger on the explicit vocabulary — "review", "code review", "quality check", "post-session review", "chimeric review", "chimera" — and on the task…
Use this skill when designing or reviewing data governance: schema ownership, PII handling, retention, lineage, access policy, and migration safety for services and data stores. Triggers: user says "data governance", "PII", "schema ownership", "retention policy", "data lineage", "migration safety".
Create and maintain coherent visual tokens, themes and shared component states using the existing project system or WrongStack Design Studio. Use when designing or substantially restyling interfaces, palettes, typography or themes; small UI fixes should extend the existing system without a kit migration.
Use this skill when writing or reviewing a Dockerfile, docker-compose setup, or container image build for a project, or when debugging a container that won't build, start, or stay healthy. Triggers: user says "docker", "Dockerfile", "container", "image", "docker compose", "containerize", "multi-stage", "distroless"…
Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".
Use when curating WrongStack SAGE memory: run deterministic hygiene and anchor verification first, then review contradictions, drift, and noise; file destructive outcomes as review proposals instead of deleting directly.
Coordinate authorized independent agent subtasks with explicit scopes, ownership and evidence. Use when delegation, a fleet, parallel agent work or result synthesis is requested or appropriate under host instructions; keep sequential or small work in one agent.
Use this skill when writing, reviewing, or refactoring Node.js code — modules, async flow, cancellation, file and process I/O, HTTP — on a current Node.js release. Triggers: user mentions "Node", "Node.js", "ESM", "CommonJS", "require", "import", "fetch", "AbortSignal", "AbortController", "stream", "childprocess"…
Use this skill when adding or reviewing logging, metrics, or tracing in an application, or when a production problem can't be diagnosed from the signals that exist today. Triggers: user says "logging", "logs", "trace", "tracing", "metrics", "observability", "instrument", "OpenTelemetry", "structured logging", "log…
Use this skill when defining or enforcing output formatting standards for agent responses in WrongStack. Triggers: user says "next steps format", "output standard", "response format", "final message format", "standardize next steps".
Create and maintain WrongStack plugins with accurate registration, configuration and lifecycle ownership. Use when implementing tools, hooks or host API extensions in packages/plugins; verify contracts from current source and test multiple instances, failed setup and reload.
Use this skill when designing, critiquing, or fixing system prompts, tool descriptions, skill definitions, or other LLM instruction text — including when a model ignores, over-applies, or misreads its instructions. Triggers: user mentions "prompt", "system prompt", "system instruction", "tool description", "skill…
Use this skill when writing, reviewing, or debugging React components and hooks — state, effects, data fetching, forms, Server and Client Components — in whatever React setup the project uses. Triggers: user mentions "React", "component", "hook", "useState", "useEffect", "re-render", "Server Component", "use client"…
Plan behavior-preserving refactors and migrations from actual dependencies, callers and tests. Use when decomposing modules, untangling coupling or sequencing a multi-file change; deliver a plan for planning requests and continue into authorized implementation when the user asked for the refactor itself.
Research current facts using primary sources, precise citations and dated evidence. Use when checking latest releases, API changes, standards, product capabilities or conflicting claims; direct known URLs can be fetched without a preliminary search.
Use this skill when the user wants a written spec, acceptance criteria, or a task graph before a non-trivial implementation, or runs the WrongStack /sdd workflow. Triggers: user says "/sdd", "spec", "specification", "task graph", "SDD", "acceptance criteria".
Review owned source, configuration and dependency metadata for supported security findings with precise evidence and remediation. Use when assessing authorization, data exposure, unsafe boundaries, credentials or advisories; treat scanner hits as candidates and scope severity to actual reachability and impact.
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: