Use when reviewing Danish copy for anglicisms, technical jargon, defensive tone, vague formulations, English words, and overly formal language. Scans uncommitted files by default or specific files with --file flag.

Review Odoo code for correctness, security, performance, and Odoo 18 standards. Use when reviewing Odoo modules, diffs, or pull requests; produce a scored report with weighted criteria.

Master the GitHub CLI (gh) for complete Software Development Lifecycle management. Use this skill when managing GitHub repositories, issues, pull requests, GitHub Projects, releases, Actions workflows, secrets, Pages deployments, wikis, Codespaces, and automating via the GitHub API. Covers the entire SDLC from terminal without browser interaction.

Review all codebase documentation files under `.claude/` and per-crate `CLAUDE.md` files, and fix any that have drifted from the actual code. This is a documentation-only task -- do not modify any source code.

>

Active orchestrator for multi-agent flight execution. Drives the full leg cycle (design, implement, review, commit) using three separate Claude instances.

Continue a project through the orchestration pipeline. Ensures the Orchestrator runs as the primary agent — not as a subagent — so it retains full control of agent sequencing. Use for local, background, or cloud-based execution.

Review a single file or all files in a folder for data inconsistencies, reference errors, typos, and unclear terminology using parallel sub-agents

Develop zgrok tunnel service following project conventions, issue specs, and Rust best practices. Use when implementing features, fixing bugs, or reviewing code in this repository.

UI design guidelines for Kubani web interfaces. Use when building or reviewing web components, pages, or the Kubani dashboard.

Use when ready to create a pull request — handles push and PR creation. Suggests security review when agent-facing code is modified.

Orchestrate the full PRD lifecycle: catchup → plan-tasks → work → review → rework loop → blind review → doubt review → done.

Review, categorize, and approve unapproved YNAB transactions via DuckDB staging + YNAB MCP

1. Read `progress.json` to get current state

Git workflow and commit conventions. Use when committing code, creating branches, or making pull requests.

1. **Review all uncommitted changes**

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

Owns the full FastAPI stack for web-cv-converter — routes, services, Pydantic schemas, Supabase migrations, Auth0 configuration. Performs OWASP self-review before every handoff.

Points agents and contributors to gc (/gc) and gcam (/gcam) skills for staging and commits with the repo Git message format. Use when the user mentions /gc, /gcam, quick commit, review before commit, or gc / gcam skills.

Reviews React and TypeScript code for correctness, security, hook usage, and multi-tenancy safety. Use when reviewing generated React components, hooks, or TypeScript files, or when asked to do a code review on frontend code.

Workflow полного health check проекта. Architecture → Security → Quality → Report → (Fix). Use before major release or onboarding.

Design a task document for a feature or bug fix through deep research and multi-round design review, and run task lifecycle workflows. Use when planning implementation work in this repository, running pre-edit `task implement` planning from a task worktree, running post-implementation `task checklist` review, resolving task docs, or purging completed task worktrees. Enforce background-doc research, codebase impact analysis, explicit first-principles/long-term/original-fit proposal lenses with tradeoffs, two formal review rounds with user feedback, strict RFC escalation for oversized scope, explicit user approval before writing docs/tasks files, and explicit developer approval before implementation edits.

Code Quality Audit

Translate or review Typst documentation TOML in this repository using the local helper, canonical repo rules, and git-based patch review.

Use when producing a read-only CoordExp audit of code, configs, specs, artifacts, docs, progress notes, or OpenSpec changes for correctness, reproducibility, pipeline, and eval-validity risks.

Use when the user needs to design, implement, audit, or govern Storybook stories for frontend components, design systems, page states, interaction tests, accessibility checks, visual baselines, or component-driven UI workflows.

Codex entry skill for request-traceable implementation planning. Use when a request needs one or more executable plan artifacts under `./plans` after resolving blocking product policy, UX, contract, schema, validation, state, permission, and any upstream UI-direction ambiguity handled by `brainstorm` or `design-discovery`, with a controller-facing `plan.md` written in plain Korean that keeps the user's request items visible, groups work by concrete boundaries, exposes public contracts before execution order, and links per-phase technical detail files for later `plan-review` and `plan-materialize`, plus registry-backed review wiki core/pattern guidance.

Strict senior-engineer code review for code changes, PRs, diffs, generated code, architecture reviews, and bug hunts. Use when asked to review quality, maintainability, structure, tests, security, performance, error handling, or production readiness.

Run `go vet` for SocialPredict backend Go code and summarize correctness-oriented findings. Use when a user asks to run `go vet`, enforce a backend quality gate, or investigate vet findings before review or verifier handoff.

Ask Claude via local CLI and capture a reusable artifact

Audit and improve CSS transition declarations. Replace generic easing with intentional curves.

Coordinates planning, implementation, review, de-sloppification, and documentation for PythonExerciseGeneratorAndDistributor changes against ACTION_PLAN.md.

Review public APIs, traits, structs, and module boundaries against the guiding

Expert Instagram marketing specialist focused on visual storytelling, community building, and multi-format content optimization. Masters aesthetic development and drives meaningful engagement. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Run safety-first repository audits for OpenClaw Bakery with evidence-based findings and low-risk remediation. Use when the user asks to audit, clean up, review operational health, or align docs/config/paths without risky architectural rewrites.

Validates story implementations through testing, code review, and quality gate assessment. Uses testing skill for execution, checks standards compliance, and creates quality gate decisions (PASS/CONCERNS/FAIL/WAIVED).

Master authentic Reddit content generator using emotion-first, phased architecture. Creates posts that sound genuinely human through cognitive state simulation, not just rule-following. Use when the user asks to write a Reddit post, create Reddit content, or needs help with Reddit engagement. Includes adversarial committee review, Claude-ism detection, and interactive refinement workflow.

Swift coding conventions and best practices for modern Swift development. Use when writing, reviewing, or refactoring Swift code to ensure consistency with naming conventions, access control, async/await patterns, and SwiftUI/framework best practices.

ai-batch-processing

Validates tests written by the tester agent. Ensures tests are meaningful, not tautological, and properly verify behavior. NEVER validates tests you wrote.

incident-management-ops

virtual-classroom-design

Code quality pillars, goals, abstraction layers, and tradeoff thinking. Use when evaluating code quality, setting quality goals, choosing abstraction levels, making design tradeoffs, or auditing code against quality pillars. Covers readability, modularity, testability, reusability, and the principle of least astonishment.

Review ADRs to check they follow testing principles and parent PDR constraints. Use when reviewing ADRs or architecture decisions.

Evaluates green bonds, sustainability-linked bonds, and social bonds with KPI selection, step-up mechanics, and framework assessment. Use when structuring ESG-linked debt, analyzing sustainability frameworks, or evaluating green bond eligibility.

Use when implementing, debugging, or reviewing code in an existing app and the user wants simple changes, reuse of existing components and design patterns, strong code quality, TDD-minded testing, and no over-engineering. Also use when deciding how much testing is needed, when validating UI changes with Agent Browser, or when simplifying a spec before coding.

Analyzes code comments for accuracy, completeness, and long-term maintainability. Detects comment rot and misleading documentation. Use after adding or modifying code comments.

Use when the user wants to convert Markdown to DOCX, make a Microsoft Word version of a Markdown file, style Word output with a reference template, fix DOCX callouts, or customize the bundled Word template for notes, reports, and review docs.

description: Run the project’s quality gates, map results to spec acceptance criteria, and produce verification_report.json with evidence and severities.

Danger JS automates pull request review chores by running programmable checks inside CI and posting structured feedback back to GitHub, GitLab, and other code hosts. It is a strong fit for teams that want to turn review conventions into repeatable checks instead of relying on humans to catch the same issues every time.