981 件 ・ 関連度順
概要と使いどころ
Generates a developer debug menu with feature flag toggles, environment switching, network log viewer, cache clearing, crash trigger, and diagnostic info export. Only included in DEBUG builds. Use when user wants a debug panel, dev tools menu, or shake-to-debug functionality.
日本語の概要は準備中です。原文の説明を表示しています。
Automatic code quality and best practices analysis. Use proactively when files are modified, saved, or committed. Analyzes code style, patterns, potential bugs, and security basics. Triggers on file changes, git diff, code edits, quality mentions.
日本語の概要は準備中です。原文の説明を表示しています。
User-facing entry point for the wp-rocket issue workflow. Invoke directly to start a delivery run from a GitHub issue number, URL, or raw description. Runs inline in your conversation context; spawns specialist agents (ticket-writer, grooming-agent, challenger, backend-agent, frontend-agent, release-agent, lead-reviewer, qa-engineer) as isolated sub-agents; invokes supporting skills (knowledge-graph, dod, docs, issue-workflow) inline. Routes based on structured JSON outputs from each agent, manages loop counters, handles escalations, and maintains a live HTML run log.
日本語の概要は準備中です。原文の説明を表示しています。
Run a lead code review on the current branch or a given PR. Standalone entry point for the lead-reviewer agent.
日本語の概要は準備中です。原文の説明を表示しています。
Review generation strategy — Request a Review, follow-up emails, insert cards, Vine, early reviewer programs
日本語の概要は準備中です。原文の説明を表示しています。
Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.
日本語の概要は準備中です。原文の説明を表示しています。
Write a PR description a reviewer can approve fast. Use when opening any pull request.
日本語の概要は準備中です。原文の説明を表示しています。
Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.
日本語の概要は準備中です。原文の説明を表示しています。
Draft, audit, or minimally revise English- or Chinese-language academic prose to reduce formulaic, vacuous, mechanically repetitive, or process-leaking language while preserving claims, evidence strength, logical relations, manuscript-wide terminology identity, document-level pattern variation, and scholarly register. Use for papers, abstracts, grants, cover letters, and reviewer responses when the user asks to de-AI, humanize, audit AI-like phrasing, or rewrite text without changing meaning. English is primary; Chinese is supported. Not for detector evasion, policy circumvention, pure translation, non-academic copy, or adding facts, citations, examples, or author experiences that the source does not contain.
日本語の概要は準備中です。原文の説明を表示しています。
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
日本語の概要は準備中です。原文の説明を表示しています。
Code review for the current change, before it is pushed. One command runs the security, secret, dependency and lint scanners that fit the changed files, a separate reviewer that checks every scanner finding and is given every changed line, and prints a short receipt with the path of the full report. Use before every git push, when asked for a code review, a security scan, or to review changes, a diff or a pull request, and when a push was blocked or warned by OpenQodex.
日本語の概要は準備中です。原文の説明を表示しています。
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers queries against the corpus, lints the graph for health, and audits in-context human feedback filed from Obsidian or the local web viewer. Use when (1) scaffolding a new knowledge base for any research topic, (2) ingesting articles/papers/PDFs/web pages into raw/, (3) compiling or restructuring wiki articles from existing raw material, (4) answering questions against the wiki and filing durable answers back, (5) running lint passes for dead links / orphan pages / coverage gaps / audit shape, (6) processing human feedback from the audit/ directory and applying corrections. Not for general note-taking, daily journals, or non-wiki Obsidian use.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture quality critique dimensions for peer review. Load when invoking solution-architect-reviewer or performing self-review of architecture documents.
日本語の概要は準備中です。原文の説明を表示しています。
Reviewer critique dimensions for peer review - implementation bias detection, test quality validation, completeness checks, and priority validation
日本語の概要は準備中です。原文の説明を表示しています。
Test design mandate enforcement, test budget validation, TDD phase validation (3-phase canon per ADR-025), and external validity checks for the software crafter reviewer
日本語の概要は準備中です。原文の説明を表示しています。
Dispatches an expert reviewer agent to critique workflow artifacts. Use when a roadmap, implementation, or step needs quality review before proceeding.
日本語の概要は準備中です。原文の説明を表示しています。
Review criteria for the nw-diverger-reviewer — validates JTBD rigor, research quality, option diversity, taste application correctness, and recommendation coherence in DIVERGE wave artifacts
日本語の概要は準備中です。原文の説明を表示しています。
Canonical AT completeness gate — research-anchored 7-category taxonomy (C1-C7) + 15-item mechanical checklist. Paradigm-neutral. Drives acceptance-designer reviewer verdict deterministically.
日本語の概要は準備中です。原文の説明を表示しています。
生成Windows批处理脚本，通过多维度检测（进程、全盘文件、注册表、已安装程序）来识别向日葵、TeamViewer等远程控制软件，并确保编码兼容性与执行稳定性。
日本語の概要は準備中です。原文の説明を表示しています。
Use when opening a pull request and the diff is cluttered with .planning/ commits. Creates a clean branch filtered of GSD planning artifacts so reviewers see only code changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.
日本語の概要は準備中です。原文の説明を表示しています。
Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants with custom prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a completed change for acceptance, regressions and release risk; read-only, not a whole-codebase audit.
日本語の概要は準備中です。原文の説明を表示しています。