4,346 件 ・ 関連度順
概要と使いどころ
Audit whether tests detect broken behavior by tracing assertions and running narrow controlled mutations in an isolated workspace; use for test-quality reviews, not routine test execution.
日本語の概要は準備中です。原文の説明を表示しています。
Verify that a requested bug fix changes observable behavior with a failing-before, passing-after reproduction and honest execution evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating and managing slash commands in Claude Code. Use when (1) creating new slash commands, (2) learning command syntax and features, (3) deciding between commands vs skills, (4) implementing advanced command features (arguments, hooks, bash execution), or (5) organizing and managing command libraries.
日本語の概要は準備中です。原文の説明を表示しています。
Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare and risk-check the next rolling-wave slice for implementation. Use when the user wants to continue a rolling-wave project, draft one bounded slice in the main context by default, use a fresh planning author only when context or discovery cost warrants it, use a fresh preparation reviewer when semantic risk or uncertainty warrants independent pressure-testing, decompose parallel implementation chunks where appropriate, identify agent, human, either, or hybrid execution fit, write or update docs/rolling-wave/{project}/slices/NNN-slug.md, and mark that slice ready even when other slices are active.
日本語の概要は準備中です。原文の説明を表示しています。
Save current Codex session to 2ndBrain vault with frontmatter, executive brief, and full transcript
日本語の概要は準備中です。原文の説明を表示しています。
Use when executing implementation plans with independent tasks in the current session
日本語の概要は準備中です。原文の説明を表示しています。
Execution pipeline for Codex. Detect epic/task/bug mode and implement with Codex models only. Usage: /implement <issue#>
日本語の概要は準備中です。原文の説明を表示しています。
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
日本語の概要は準備中です。原文の説明を表示しています。
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
日本語の概要は準備中です。原文の説明を表示しています。
Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation planning workflow using the plan template to generate design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Produce a flow-level summary of the current Claude Code session — executive summary, chronological timeline, and outcomes — written into the active feature directory next to spec.md / plan.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
日本語の概要は準備中です。原文の説明を表示しています。
Execute the implementation planning workflow using the plan template to generate design artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).
日本語の概要は準備中です。原文の説明を表示しています。
Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows. Use when asked to summarize recent Codex bug reports or enhancement requests, especially for owner-specific labels such as tui, exec, app, or similar areas.
日本語の概要は準備中です。原文の説明を表示しています。
How to run tests using remote executor.
日本語の概要は準備中です。原文の説明を表示しています。
Design relational database schemas (and choose when to go NoSQL) that stay maintainable and fast. Use this skill whenever the user mentions tables, DDL, entities and relationships, normalization (1NF/2NF/3NF), primary and foreign keys, UUID vs bigint IDs, indexes (B-tree, composite, covering, partial), EXPLAIN, constraints (CHECK, UNIQUE, exclusion), transactions and isolation levels, migrations (Alembic, Prisma, Flyway, expand-contract, backfilling), or SQL vs NoSQL (MongoDB, DynamoDB, Cassandra, graph databases). Also trigger for "design the database", "model this domain", "which database should I use", or writing ORM models and migration files for PostgreSQL, MySQL, SQLite, or SQL Server.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically find and fix performance problems in applications, frontend and backend, by measuring first. Use this skill whenever the user reports slow endpoints, high latency, poor throughput, memory leaks, large bundles, or slow page loads; wants to profile with cProfile, py-spy, Chrome DevTools, Node --cpu-prof, or perf; run load tests with locust or k6; set performance budgets or SLOs; optimize database queries (EXPLAIN, indexes, N+1); add caching (Redis); improve frontend performance (code splitting, lazy loading, image optimization, memoization, virtualization); or tune the network (CDNs, gzip/br, HTTP/2/3). Also trigger for p50/p95/p99 latency, throughput, error rate, connection pooling, async vs threads, GIL, and memory leak investigations.
日本語の概要は準備中です。原文の説明を表示しています。
Find, build, evaluate, and improve systems using decision models. Use for bounded classification, routing, ranking, Choice/Score/Noul, decision-model composition, evaluation harnesses, prompt/program hill climbing, and Software 3.0 workflows across software, business, organizations, and life. Separate models, code, and human judgment. TypeSafe Jev is the default hosted exemplar. Not for straightforward arithmetic, prose rewriting, or provider setup alone.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in Claude Code with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in ZCode with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。