Menü
Skeptical staff-engineer code review of changed files against coding-standards.md.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Reference for Claude Code's own mechanics — slash commands, skills, subagents, hooks — and how they route together. Use when creating or editing a slash command, skill, subagent, or hook, or when deciding which primitive fits a task.
Verify Sentry error capture is working after a DSN change or deploy. Use when testing Sentry, confirming error reporting works, or debugging why errors aren't showing up in the Sentry dashboard.
Sanity-check the working tree before starting plan execution or new branch work. Catches inherited damage that silently breaks verification later — merge conflict markers committed to tracked files, outstanding stash entries that may bleed into your work, uncommitted changes you may not realize you have. Runs in ~1 second. Trigger BEFORE invoking superpowers:executing-plans or superpowers:subagent-driven-development, BEFORE creating a new feature branch off main, or when verification mysteriously fails on files you did not touch.
Syncs main and deletes the local feature branch after a PR is merged on GitHub. Use when the user says they merged or squash-merged a PR ("I merged PR 411 on GitHub", "merged the PR", "clean up the branch"). Codifies this repo's squash-merge default, where `git branch -d` wrongly reports "not fully merged" and a verified force-delete is required.
Apply the Inkwell design system to an existing page or component without creating a competing styling system. Use for styling retrofits, standalone HTML explainers, docs pages, or Tailwind v4 token alignment.
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, or editing any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
| name | source-command-qcheck |
| description | Skeptical staff-engineer code review of changed files against coding-standards.md. |
Use this skill when the user asks to run the migrated source command qcheck.
Review all changed files in this session as a skeptical staff engineer for the gsd-taskmanager codebase. Apply the full coding-standards.md and AGENTS.md rules.
Run git status and git diff first to see what has changed. Then evaluate each changed file against:
any without justification, Zod validation at boundaries (user input, import, MCP tool inputs).toast.error() from sonner instead of window.alert().client_updated_at (not updated) in sort/filter, _superusers admin endpoint, 100ms push throttle, batch lookups not N+1..safeParse() (not .parse()) on user input paths; import uses .strip(), export uses .strict().bun run test (not bun test); localStorage.removeItem(key) (not clear()).toast.error() (not alert()); accessibility baseline from coding-standards Part 2.lib/logger.ts, no console.* in production paths, no PII in logs.Distinguish blocking issues from suggestions. Prefix non-blocking comments with nit: or suggestion:.
Do not rewrite the code. Return a structured list of findings, organized by file, with file:line — issue — fix.