「docs」の検索結果

Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx-review or /phx-investigate.

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

Document tested Elixir APIs; may update README/ADRs. Not for docs lookup, audits/reviews, or standalone decisions.

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

Searchable Elixir/Phoenix/Ecto solution documentation system with; Use when consulting past solutions…

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

Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful…

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

Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.

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

Recall prior work from past sessions — how a bug was fixed, what was decided, where a pattern lives. Use when asked 'have we done this before' or 'how did I fix X' in Elixir/Phoenix work. ccrider MCP when available, else git + solution docs.

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

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

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

Research Elixir/Phoenix/Ecto topics or evaluate Hex libraries (--library). Use when learning about libraries, patterns, or comparing approaches. Searches HexDocs, ElixirForum, GitHub.

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

Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful phx-review or phx-investigate.

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

Use when asked to document Elixir code: add or fill in @moduledoc and @doc for modules and functions. Documents tested code only; may add a README section or ADR. Not for docs lookup or audits.

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

Research Elixir/Phoenix/Ecto topics or evaluate Hex libraries (--library). Use when learning about libraries, patterns, or comparing approaches. Searches HexDocs, ElixirForum, GitHub.

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

Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.

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

Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.

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

Use when asked to document Elixir code: add or fill in @moduledoc and @doc for modules and functions. Documents tested code only; may add a README section or ADR. Not for docs lookup or audits.

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

CONTRIBUTOR TOOL - Validate plugin against latest Claude Code documentation. Catches breaking changes, deprecations, discovers new features. Run before releases or periodically. NOT part of the distributed plugin.

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

Mines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, the `AGENTS.md` files, and `.agents/rules/` — proposing edits first and applying only with the user's approval. TRIGGER when: the user wants to turn PR review feedback into durable conventions, guidelines, or rules; capture recurring reviewer comments as internal documentation; or check whether review lessons are reflected in the knowledge/guides/guidelines/AGENTS.md/rules layer. DO NOT TRIGGER when: sweeping a feature's changes for documentation coverage across all layers → use `audit-docs`; extracting knowledge from completed spec directories → `speckit-opsmill-extract`; only replying to or resolving review threads → normal git/gh flow.

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

Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.

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

Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.

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

Pre-search topic resolution. Maps vague queries to concrete entities (GitHub orgs, X handles, subreddits, docs URLs) before searching. Run as first step of any research workflow to dramatically improve search precision.

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

External research workflow for docs, web, APIs - NOT codebase exploration

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

Release preparation workflow - security audit → E2E tests → review → changelog → docs

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

Search library documentation and code examples via Nia

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

Single page smart extraction - articles, docs, blog posts to clean markdown

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

오픈소스 릴리스 위생 루틴. 새 기능/스킬/에이전트를 추가했을 때 (1) 부산물(v1/v2 .bak, _source, 로그, scratch dir)이 changeset에 없는지, (2) 문서(README/docs/home)가 동기화됐는지, (3) npm 배포 대상인지(skills/ + files vs .claude local-preview) 판단했는지 체크리스트로 강제. '릴리스 준비', '커밋 전 점검', 'push 전에 정리', '배포 위생', 'release hygiene' 류 트리거. husky pre-commit이 부산물 게이트를 자동 실행.

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