Use when selecting a Mermaid diagram type, looking up Mermaid syntax, adapting a Mermaid example, or locating a Mermaid reference for a flowchart, sequence, UML, architecture, chart, or other diagram.
日本語の概要は準備中です。原文の説明を表示しています。
Use when selecting a Mermaid diagram type, looking up Mermaid syntax, adapting a Mermaid example, or locating a Mermaid reference for a flowchart, sequence, UML, architecture, chart, or other diagram.
日本語の概要は準備中です。原文の説明を表示しています。
Assess review findings against the target's governing contract, evidence, and consequence without imposing a lens-specific verdict, schema, or gate. Use when classifying a candidate concern in a code or change review.
日本語の概要は準備中です。原文の説明を表示しています。
Decide whether to adopt, adapt, or justify building a new script, tool, utility, library, module, dependency, or bespoke capability. Use in task planning, worker execution (including tooling discovered after planning), or code review when an implementation choice may duplicate an existing solution.
日本語の概要は準備中です。原文の説明を表示しています。
Relay agent results without corrupting exact counts, failure reasons, source scope or status. Use when receiving agent output or handing results to another actor; distinguish observations from attributed conclusions and reference complete artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Research a specific technology, library, system, protocol, or tool to answer a concrete technical question with source-traceable evidence. Use when current implementation details, version behavior, configuration, compatibility, or authoritative technical facts must be verified rather than recalled. Also use when explicitly asked to incorporate verified findings into an existing skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks what to do next, asks for a plan under uncertainty, challenges stalled or low-trust work, requests multiple possible approaches before action, or needs an evidence-first loop that uses RT-ICA-style prerequisite checks, adversarial review, subagent coordination, real validation, and durable concern tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize a supplied URL from fetched content with source locations, acquisition coverage and explicit access failures. Use for articles, documentation, API references and web pages; preserve version, author attribution and uncertainty in the requested output format.
日本語の概要は準備中です。原文の説明を表示しています。
Illustrative Claude Code skill configuration. Use when learning the basic SKILL.md shape; follow the canonical runtime reference for the current field inventory.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
日本語の概要は準備中です。原文の説明を表示しています。
Start a local Git rebase when the user explicitly requests replay of a named source ref, or of the current branch, onto a named target, including a rebase-then-push request, which carries exact-lease publication to the branch's own remote destination, or continue or abort an active rebase. Use only when local history replay will start or is active; do not use for merge-based branch updates, repository merge settings, pull-request or merge-request merging, or push-only requests.
日本語の概要は準備中です。原文の説明を表示しています。
Assess and address review feedback on GitHub PRs, GitLab MRs, or in conversation. Use when checking new reviews, responding to comments, rechecking after a push, or following up on approvals and change requests.
日本語の概要は準備中です。原文の説明を表示しています。
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the primary outcome is authoring, rewriting, summarizing, or validating user-facing documentation without implementation comparison or required source attribution, including READMEs, tutorials, API docs, GitLab Markdown, source-faithful summaries, and audience-specific prose.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize files or a requested directory scope from actual contents. Extract code, config, data and document evidence, preserve exact counts and source locations, and disclose incomplete or unsupported acquisition. Use for file summaries, code explanations and configuration overviews.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the primary outcome is creating publishable source-attributed content from URLs or supplied material, including research summaries, articles, briefs, and posts whose factual claims and quotations need reader-visible, verifiable citations.
日本語の概要は準備中です。原文の説明を表示しています。
Describe images, screenshots, diagrams and charts from visual inspection. Preserve visible text, counts, labels, directions and uncertainty; distinguish observation from interpretation. Use for image summaries, screenshot explanations and diagram descriptions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or backfilling AI-categorized daily GitHub releases from branch commits.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly asks Rewrite Room to route documentation work, or when audit/sync/freshness, user-facing authoring, citation-driven writing, docs-to-skill conversion, and AI-instruction optimization overlap and exactly one workflow must be chosen.
日本語の概要は準備中です。原文の説明を表示しています。
Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.
日本語の概要は準備中です。原文の説明を表示しています。
Ensemble SOLID review — fans the ruleset across overlapping focused workers over the same code, then reduces by corroboration.
日本語の概要は準備中です。原文の説明を表示しています。
Single-pass SOLID review — dispatches one reviewer over the complete ruleset, emitting the fixed candidate schema.
日本語の概要は準備中です。原文の説明を表示しています。
Design, build, evaluate, or teach graph-based systems. Use for knowledge graphs, ontology/schema design, entity/relation/event extraction, entity resolution and fusion, GraphRAG or graph memory, and agent/task dependency graphs with concurrency, joins, failure handling, verification, or human gates.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate multiple source findings into an attributed synthesis or comparison. Use for combine these summaries, synthesize results, merge findings or multi-source analysis. Preserve claim-level provenance, coverage, qualifiers, conflicts and uncertainty rather than repeatedly compressing narrative summaries.
日本語の概要は準備中です。原文の説明を表示しています。