「nes」の検索結果

Search, create, and manage notes in an explicit Obsidian vault with title-case filenames, wikilinks, index notes, backlinks, and safe vault-root confirmation.

日本語の概要は準備中です。原文の説明を表示しています。

Set up repository-local Husky pre-commit hooks with lint-staged, Prettier, and optional typecheck/test gates. Use when a user asks to add pre-commit hooks, configure lint-staged, enforce staged formatting, or add commit-time checks.

日本語の概要は準備中です。原文の説明を表示しています。

Generate structured weekly status reports covering initiatives, progress, blockers, risks, and KPIs.

日本語の概要は準備中です。原文の説明を表示しています。

Reference definitions for the Agent Forge orchestration roles (lead, worker, planner, evaluator). Use when coordinating multi-agent Forge work or when you need one role's responsibilities and constraints.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate a reported problem, diagnose root cause, and file a Beads issue with a behavior-level TDD fix plan.

日本語の概要は準備中です。原文の説明を表示しています。

Classify a task and route it to the right workflow (fix / feature / epic). Use when the user runs /go or wants the adaptive workflow router.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 4 of the Forge pipeline. Summarize the whole workload — what was built, which Beads issues closed, a before/after, and a step-by-step walkthrough the user can run to verify it themselves — then run quality gates, push, and open the PR. Use when starting /forge-ship or the ship step of /forgemaster.

日本語の概要は準備中です。原文の説明を表示しています。

Multi-repo git operations — init, reset, status, branch management, refresh (rebase), stacked rebase. JSON output for agent consumption.

日本語の概要は準備中です。原文の説明を表示しています。

Migrate test files from `as` assertions to @total-typescript/shoehorn helpers. Use when tests need partial fixtures, intentionally invalid data, or safer replacements for TypeScript assertions.

日本語の概要は準備中です。原文の説明を表示しています。

Relentlessly stress-test a plan or design through a one-question-at-a-time interview that researches available context first and includes a recommended answer with every question. Use when the user asks to "grill me", wants a plan/design challenged, or needs decisions resolved before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Scaffold course exercise directories with numbered sections, exercise variants, required readmes, and repo-specific validation. Use when creating exercise stubs, adding a course section, or safely renaming exercises.

日本語の概要は準備中です。原文の説明を表示しています。

Route a task by complexity and run the gated Forge pipeline (research → plan → implement → ship). Use when the user runs /forgemaster or wants the full guided feature pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

Set up Claude Code git safety guardrails that block dangerous git commands before execution. Use when the user asks to prevent git push, hard reset, git clean, destructive checkout/restore, or branch deletion from Claude Code hooks.

日本語の概要は準備中です。原文の説明を表示しています。

Run the full Forge pipeline unattended: each phase is reviewed by a fresh evaluator subagent, the findings feed back, and the run advances itself. Use when the user runs /forgemaster-auto or wants a feature built end to end without approval gates.

日本語の概要は準備中です。原文の説明を表示しています。

Stress-test a plan against existing domain language, code behavior, and durable decisions. Use when the user wants DDD/domain-model grilling, glossary refinement, terminology challenges, context documentation, ADR candidates, or plan validation against a repo's language.

日本語の概要は準備中です。原文の説明を表示しています。

Extract a DDD-style domain glossary from conversation context, choosing canonical terms and flagging ambiguity. Use when the user asks to define domain terms, build a glossary, clarify terminology, create a ubiquitous language, or mentions domain modeling or DDD.

日本語の概要は準備中です。原文の説明を表示しています。

Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.

日本語の概要は準備中です。原文の説明を表示しています。

Fact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.

日本語の概要は準備中です。原文の説明を表示しています。

Edit and improve article drafts by confirming a heading-based section plan, dependency order, then rewriting section by section with short paragraphs. Use when the user wants to revise or improve an article draft.

日本語の概要は準備中です。原文の説明を表示しています。

Auto-capture UI screenshots for PRs using Playwright MCP browser tools.

日本語の概要は準備中です。原文の説明を表示しています。

Deadline management and capacity planning across epics and PRs. Use when the user runs /triage or wants deadline/capacity triage.

日本語の概要は準備中です。原文の説明を表示しています。

Add focused Bun unit tests for mission-critical behavior and edge cases — not blanket coverage.

日本語の概要は準備中です。原文の説明を表示しています。

Generate multiple radically different interface designs before implementation. Use when designing an API, module boundary, command surface, data contract, or when the user says "design it twice".

日本語の概要は準備中です。原文の説明を表示しています。

Auto-generate knowledge YAML from the codebase. Use when the user runs /sync-knowledge or wants knowledge files refreshed.

日本語の概要は準備中です。原文の説明を表示しています。