professor-for-testing-agentic-qe-skill-builder
Build comprehensive testing skills with TDD, quality engineering, and automated test generation. Use when creating test suites or improving testing practices.
react-component-create
Create new React components following project patterns and best practices. Includes proper typing, testing, and documentation.
resilience-check
Checklist for reliability engineering
security-audit
Procedure for analyzing code or dependencies for vulnerabilities
test-suite-create
Creates a comprehensive test suite for a feature
typescript-refactor
Safely refactor TypeScript code while maintaining type safety and test coverage. Includes verification steps.
bonsai
Maintain and groom config files in the current repository. Use when reviewing config health, pruning unused entries, fixing cross-file inconsistencies, applying format changes after tool upgrades, or doing periodic config tidy-up. Not for code quality review of application source.
cross-browser
Use when verifying page rendering or behavior in Safari (WebKit), Firefox, or across multiple browser engines. agent-browser is Chromium-only via CDP; these checks require playwright-cli. Not for Chromium-only verification — use agent-browser there.
decision-log
Persist a decision that has just been settled — the alternatives rejected, the reasoning, the consequences accepted, and the condition for revisiting it — into one database shared by every repository, and retrieve past ones from any of them. Use at the moment a design, architecture, or tooling choice stops being weighed and becomes what will be done, and whenever the alternatives or rationale behind an earlier choice are asked for, including a choice settled while working somewhere else. Not for choices without meaningful trade-offs.
design-conformance
Make new UI look like it belongs in the product that already exists: read the design tokens and components the codebase declares, or where nothing is declared, the conventions its existing screens already follow, and compose within them instead of introducing a fresh aesthetic. Use when adding to or revising a surface that ships beside other screens, and when reviewing UI just written for values invented outside the system. Not for greenfield work where a distinctive, one-off look is the point, not when the brief asks for a new look rather than a consistent one, and not for a codebase that has no UI yet.
devils-advocate
Examine a direction the user has already settled on from both sides at once, each side argued by an independent agent that sees neither the other nor the assessment forming in this conversation. Use before answering someone who presents a course as decided and asks whether to proceed — whether the answer taking shape is agreement or rejection, and above all when the course is the user's own and agreeing would cost nothing — to surface what it rests on and what would settle it. Not for an option still being floated, where no course has been chosen yet. Reports whichever side holds, including when only one does.
external-repo
Use whenever you decide you need to inspect a third-party repo's source on disk — explicit (user pastes a repo URL asking about its contents, "how is X implemented in library Y") or implicit (you yourself proposing mid-conversation to fetch an OSS project to investigate). Managed via ghq for direct Read/Grep. DO NOT USE for one-off doc/raw-file lookups (WebFetch) or work inside the user's own repo.
japanese-writing
Revise Japanese developer-facing technical writing — planning/design docs, meeting materials, issue/PR text, team chat posts — to read plain and accurate: cut overstatement, coined jargon, filler, and blame aimed at people; fix loose paragraphs and notation (spacing around half-width alphanumerics). Use when writing or editing such Japanese prose, including small edits to already-drafted or posted text. Not for English, reference docs, or CLI text.
pr
You MUST invoke this BEFORE running `gh pr create` or `gh pr edit`, and any time the user expresses intent to ship branch work upstream — explicit ("create PR") or implicit ("push this", "ship it", or you yourself proposing to push after completing work). DO NOT USE for leaving inline review comments on an existing PR.
refutation
Verify a finished artifact by dispatching an independent skeptic that never saw it being made, tasked with refuting it, grounding every factual claim in a primary source, and reporting findings with severity and confidence. Invoke before handing over any deliverable that has no automatic falsifier — documents, rules, guidelines, skills, plans, analyses, decisions — above all one produced in the current session. Code already covered by tests, typecheck, or lint has a falsifier; use it there only for claims those checks do not exercise. Not for wording, style, or "does this look OK" passes.
review-prep
Prepare a human reviewer to review someone else's pull request — machine-check verbalizable perspectives with subagents, then hand over a self-contained HTML briefing separating what is safe to skim from what needs the human's design judgment. Strictly read-only against GitHub. Use when the user will themselves review someone else's PR — assigned as reviewer, asking where to start reading before passing judgment, or merely stating they have to review a PR (a bare URL or number with no explicit ask). Not for fully automated review that ends with AI findings, and not for responding to feedback on the user's own PR.
skill-eval
Evaluate and tune an LLM-facing instruction doc — a skill, subagent prompt, or CLAUDE.md/rule addition — by having a fresh subagent execute it blind against frozen scenarios and iterating fixes until improvements plateau. Use right after authoring or substantially revising such a doc, or when a skill misbehaved and instruction-side ambiguity is suspected rather than model failure. Not for typo-level wording changes or personal-taste polish.
socratic
Interview the user one question at a time to turn a half-formed idea into a plan they own. Use when the user muses a tentative idea of their own ("maybe I should X", "I'm thinking of X") rather than asking for a verdict — develop it by questioning, not by recommending; also for pressure-testing a plan decision-by-decision. Not for explicit requests for a recommendation, plain build requests, or rubber-stamping a finished plan.
tdd-first
Pin the expected outcome down as a failing test before writing production code. Use when a change alters observable behavior — new logic, a bug fix, a modified rule. Not for config, docs, or refactors that keep behavior identical.
test-perspectives
Use when writing or expanding tests for code with branching conditions, state transitions, input boundaries, or operational failure modes.
speclet-draft
Generate a collaborative draft document with clarifying questions for a new feature
speclet-learn
Generate explanatory lessons after completing speclet stories to develop mechanical coding fluency
speclet-spec
Convert a draft document into an executable spec.json with trackable stories
speclet-ticket
Convert a large draft into individual tickets for isolated implementation sessions
speclet-council
Run parallel reviews on draft/spec/ticket inputs and emit Council artifacts
speclet-loop
Execute one autonomous iteration - implement the next story from spec.json
simple-task-management
This skill should be used when the user asks to "generate tasks from a spec", "break down a spec", "create tasks from a PRD", "decompose requirements", "generate a task list from a design document", or mentions working from specification documents. Provides guidance for transforming specifications into structured, actionable task lists organized under missions.
spec-task-management
This skill should be used when the user asks to "analyze a specification", "break down a spec", "create tasks from a PRD", "decompose requirements", "generate a task list from a design document", or mentions working from specification documents. Provides comprehensive guidance for transforming specifications into structured, actionable task lists optimized for AI coding agents.
workbench-quality
Generate and inspect repo-native testing evidence for Workbench quality reports.
workbench-architecture
Architecture workflows for Workbench CLI. Use when documenting system design, tradeoffs, or rationale in canonical architecture artifacts.
workbench-github
GitHub workflows for Workbench CLI. Use when creating pull requests from work items or wiring GitHub-specific actions.
workbench-docs
Documentation workflows for Workbench CLI. Use when creating or updating specs, architecture docs, verification docs, runbooks, guides, or general docs, and when syncing backlinks or change notes.
workbench-sync
Sync workflows for Workbench CLI. Use when aligning local work items with GitHub issues, creating branches, or reconciling doc backlinks.
workbench-work-items
Work item management for Workbench CLI. Use when creating, updating, linking, or closing work items and tracking execution status.
context7-search
Retrieve real-time technical documentation and code snippets from third-party libraries using the Context7 V2 API.
kana-review
>-
anipy-cli
This skill should be used when the user asks to play, watch, stream, search, download, or binge anime; continue watching or check anime history; install, setup, configure, update, or fix anipy-cli; change video player or set anime quality; troubleshoot anime playback issues; or mentions anipy-cli by name. Triggers on "play anime", "watch frieren", "stream one piece dubbed", "download anime episodes", "binge naruto 1-10", "show anime history", "next episode", "continue watching", "change player to mpv", "set quality to 1080", "anipy-cli not working", "player not found", "anipy-cli", "anime from terminal".
suno
This skill should be used when the user wants to compose songs for Suno AI, write lyrics, create style prompts, or generate Suno metatags. Supports J-pop, K-pop, EDM, ballads, rock, and Latin genres, plus album/EP composition, variations, and song continuations. Also handles reference-based composition ("like YOASOBI", "in the style of Aimer") and J-pop tier presets ("anisong", "mainstream", "doujin"). Triggers on "write a song", "Suno prompt", "Suno metatags", "style of music", "song lyrics", "Suno AI", "acoustic version", "create an album", "extend this song", "like [artist]", "in the style of", "/suno", "anisong", "doujin", "negative prompting", "ad-libs".
project-init
|
dev-workflow
|
file-issue
|
agents-md-generator
Automatically generate comprehensive AGENTS.md files that teach AI agents how to work with a repository's structure, conventions, and guidelines
caps-format-validator
Validate CAPS (Coding Agent Playbook Spec) playbooks for correctness, completeness, and compatibility with Claude Code and Goose
kubernetes-health-check
Verify Kubernetes cluster health, resource availability, and readiness before deploying applications
mcp-toolbox
Use when working with or extending the local Codex MCP toolset/server that exposes HTTP endpoints for shell, filesystem, git, and Excel operations, or when a task should be executed by calling those MCP endpoints instead of local tools, especially if the MCP server is running.
init
Initialize or update the project using the `specify` CLI (--refresh for templates, --update to upgrade CLI, --clear to reset status line). Do NOT search for speckit or spec-kit binaries.
adr-ship
This skill should be used when the user wants to "implement an ADR",
create-adr
This skill should be used when the user asks to "create-adr", "課題を追加して", "ADR作って", "issueに追加して", or describes a problem/pain point they want to track. Creates an entry in docs/issues.md and a corresponding Draft ADR in docs/adr/.
evaluate-adr
ユーザーのプロンプトを評価してADRとして記録すべき意思決定が含まれているかを判断する。create-adr スキルから内部的にコールされる。
codex-sync
>-
Page 1306 of 1666 · 83262 results