yuya296

Docker 内の `playwright-cli` 実行に限定した補助 skill。named session の利用、スクリーンショット再利用、container profile 前提の操作に絞る。

Use when verifying this repository's Slack bot behavior by actually sending image-attached DMs in Slack Web, especially with `docker compose up -d --build` and `playwright-cli` against the CodexAgent DM thread.

Use when adding, renaming, reorganizing, or reviewing tests in this repository, especially when the goal is to make tests readable as specification and align them with module boundaries and behavior-first descriptions.

Decide whether a decision in a user-agent conversation should be recorded as an ADR, and create the ADR when needed. Use when the conversation includes a decision signal (e.g., "OK", "let's do that", "その方針で行こう") and you must judge ADR necessity, then write a new ADR under docs/adr with the required template.

Root-cause-oriented bug fixing workflow with lateral impact investigation and recurrence-prevention guardrails. Use when users ask to fix defects/bugs and want analysis beyond immediate symptoms, horizontal scans for similar faults, and concrete prevention actions such as test additions, validations, static checks, and process safeguards. Trigger especially on requests like "根本原因", "水平展開", "再発防止", "ガードレール", "不具合修正の進め方".

Automate the "git status → diff summary → Japanese commit message → git commit" workflow. Use when a user wants Codex to review pending changes, describe the diff, draft a Japanese commit message, and perform `git commit` after confirmation.

完了報告前のDefinition of Done確認ワークフロー。Codexが内部的に「実装完了」と判断した時点で起動し、DoD項目の充足確認と報告フォーマット統一を行う。ユーザから完了報告依頼が来た場合も同様に適用する。

実装着手時の標準ワークフロー。ユーザが「実装開始」「着手」「進めて」「ブランチ切って実装」など実装開始を求めたときに使い、着手チェック、作業計画の明確化、影響範囲確認、実装前の検証計画を短時間で確定する。

Add support for a new AI chat site in the Awesome Input repository by following the project-specific adapter workflow. Use when the task is to add, update, or review support for another site, plugin-like target, hostname, or editor implementation in this codebase.

Create Scrum planning PBIs and docs under docs/features. Use when the user asks to plan work, split backlog items, or says phrases like "PBI作って", "スクラムのプランニングして", or "Backlog切って". Produces PBI folders with spec.md, todo.md, and test.md without implementing code.