Create, edit, or review AGENTS.md and CLAUDE.md repository instructions. Use for agent instruction setup and structure advice, not ordinary code changes that merely read those files.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Write repository instructions that help an agent make decisions it cannot reliably infer from the code, tooling, or existing documentation.
Use the filename, location, and format the user requested. For an edit, keep the existing format and structure unless the requested improvement calls for changing them. Do not ask the user to choose again.
For a new document with no specified format, inspect the repository's existing instruction files and target tools. Ask only if the intended tool or scope remains ambiguous and would change the result. Read the relevant format reference when selecting a format or changing loading, imports, or nested instructions:
Review-only requests produce findings; creation and editing requests produce the requested file changes. Do not rename files or change other tools' configuration as an incidental part of an edit.
Inspect applicable parent and nested instructions, relevant project documentation, package manifests, scripts, and CI configuration. Use them to establish actual commands, scope, and conventions; do not invent missing project policies.
Keep existing requirements unless they are obsolete, contradictory, or within the requested policy change. Preserve concrete safety boundaries and fragile-operation constraints when shortening prose. If evidence cannot resolve a material conflict, identify it rather than silently choosing a new policy.
Choose sections for the repository's needs. Useful content may include non-obvious architecture, commands and prerequisites, testing contracts, compatibility requirements, and links to task-specific documentation. A small edit does not require a full document rewrite or a directory tree.
Do not impose template defaults for compatibility, dependencies, test strategy, commit format, or language. Record the project's decisions. Avoid duplicating rules already enforced by tooling unless agents need instructions for running that tooling or handling exceptions.
For a new document, assets/template.md provides optional headings. Replace placeholders with verified information and omit unused sections. For a broader structure review, read references/best-practices.md.
Check changed commands against their definitions and working directories, verify referenced paths, and review applicable instructions for contradictions. Run commands when safe and useful to validate a changed instruction; document any unverified behavior without claiming it was tested.
Confirm that the result fits the requested scope, retains necessary constraints, and does not add unrelated policy. Report the changes and any unresolved ambiguity.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create, update, or review Architecture Decision Records (ADRs) using the project's conventions. Use when asked to record an architecture decision or work on an ADR; not for general design discussion without a requested record.
The English summary is being prepared. Showing the original description.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking or requests an in-depth interview with dig.
The English summary is being prepared. Showing the original description.
Discuss ideas and design choices before implementation, without editing files.
The English summary is being prepared. Showing the original description.
Clone 済みのこの環境リポジトリのルートで実行し、setup.yaml(唯一の真実)と dotfiles/、skills/ を基準に端末上の dotfiles、Claude/Codex skills、関連 CLI 設定を安全に同期・更新・整理する。Use when the user asks to set up, reconcile, migrate, update, clean, prune, or merge this repository's dotfiles or skills with an existing terminal, especially when existing local files must be inspected before applying repository versions.
The English summary is being prepared. Showing the original description.
remote の rebase や force-push 後に diverge した gh-stack を診断し、local state を退避して remote に合わせて再構築する。履歴書き換えが疑われる non-fast-forward の調査と復旧に使う。通常の sync や一般の Git branch 管理には使わない。
The English summary is being prepared. Showing the original description.
PR 作成を依頼されたときに、依頼範囲の変更を確認し、リポジトリのテンプレートに沿ったタイトルと本文で GitHub PR を作る。本文の下書きだけを求められた場合は公開しない。
The English summary is being prepared. Showing the original description.