Repository navigation
feat(breezing): startup plan narration — relax UX hard contract - #190
Conversation
v4.13.2 の Narration Rules が「最初の text は 1 行のみ・中間ナレーション 一切禁止」と振り切れすぎ、起動後に何も表示されず「今から何をするのか 分からない」状態だった。3 skill (breezing / cursor-ask / cursor-do) の Narration Rules を「計画明示型」に緩和: - 起動時に banner + 実行計画 (2-4 step、合計 5 行以内) を明示してから実行開始 - 見やすい進捗報告 (各ステップ 1 行ステータス / 判断に必要な中間結果 / 1 行の経緯) を明示的に許可 - 禁止は冗長さ (同じ事実の 2 回言い換え / 中身のない前置き / 3 行以上の 経緯振り返り / 起動シーケンス中の Insight ブロック) のみに限定 breezing の Cursor Backend Fast Path / Reviewer-only mode の flow 記述、 cursor-do の Step 0/1 も banner + plan に整合。mirror (opencode / codex) 同期、validate-plugin 101/101 + check-consistency 全合格。 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (2)
ウォークスルーv4.13.2 の過剰な表示抑制を緩和し、/breezing・/cursor:ask・/cursor:do の起動時ナレーションを「計画明示型」へ統一。起動時に banner + 実行計画（最大5行以内）を明示し、進捗報告の許容粒度と禁止事項を再定義。複数スキルファイルの Narration Rules と Execution Flow を対応更新。 変更内容起動時ナレーション規約の段階的緩和
Sequence Diagram（起動->計画->実行の高レベルフロー）sequenceDiagram
participant Caller
participant Skill as Skill_Module
participant Backend as Executor
Caller->>Skill: 起動要求
Skill->>Skill: banner と plan を生成（1行 + 2-4行、合計5行以内）
Skill->>Caller: banner + plan を出力（短時間）
Skill->>Backend: Step1 を開始
Backend->>Caller: 各ステップの1行ステータスを返す
🎯 3 (中程度) | ⏱️ ~20 分関連する可能性のある PR
詩
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bdb6cffe72
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### Step 0: 起動時 banner + plan | ||
|
|
||
| 上記 Narration Rules を厳守する。3 秒以内に Step 1 へ。 | ||
| 上記 Narration Rules に従い、banner + 計画 (3 行以内) を出してから Step 1 へ。 |
There was a problem hiding this comment.
When /cursor:ask is invoked, this new Step 0 tells the agent to emit the banner plus plan before continuing to Step 1, but Step 1 still says the first text is exactly the one-line banner. Following the documented flow now either repeats the banner or skips the required plan, which defeats the startup UX contract this change is trying to define. Please fold the plan into the Step 1 example or remove the separate one-line banner step.
Useful? React with 👍 / 👎.
| ``` | ||
|
|
||
| `<current-branch>` は Step 2 で取得する値だが、Step 1 では未取得のため `…` でも可。Step 2 直後に確定値を 1 行で再出力する。**この echo 以外の text を Step 2 まで一切出さない。** | ||
| `<current-branch>` は Step 2 で取得する値だが、Step 1 では未取得のため `…` でも可。Step 2 直後に確定値を 1 行で再出力する。Step 0 の banner + 実行計画 (5 行以内) はここで出し切り、以降は各ステップの 1 行ステータスで進捗を見せる。冗長な繰り返しのみ避ける。 |
There was a problem hiding this comment.
For /cursor:do calls with arguments, Step 1 still instructs an immediate one-line echo and shows only the banner, while this added sentence says the banner plus execution plan should be emitted here. Agents following the code block will omit the required plan, and agents following this sentence will violate the surrounding “first text echo (1 行)” instructions. Please update the Step 1 heading/text/example so the banner and plan are a single unambiguous startup output.
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 9
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 9-15: The CHANGELOG entry under "### Changed" describing the
Narration Rules change for `/breezing` / `/cursor:ask` / `/cursor:do` needs a
Before/After table added (and mirrored in the `[Unreleased]` section) so readers
can quickly see the behavioral delta; update the relevant entry text for v4.13.2
(the paragraph referencing "起動ナレーションを「計画明示型」に緩和" and the bullet examples) by
inserting a concise two-column Before / After table that shows the previous
behavior ("1-line banner only, no intermediate narration, immediate delegation")
versus the new behavior ("banner + 2–4 step execution plan, per-step 1-line
status reports, allow minimal intermediate results, block only verbose
repetition/Insight blocks"), and ensure the `[Unreleased]` heading contains the
same Before/After table for this change.
In `@codex/.codex/skills/cursor-ask/SKILL.md`:
- Around line 40-43: The fenced code blocks in SKILL.md (the blocks shown around
the "🚀 cursor / composer-2.5-fast / ask" example and the other examples at the
same section) are missing a language identifier and violate MD040; update each
triple-backtick fence (the blocks currently like ``` ) to include a language
label (e.g., ```text) so they match the original/mirror file and fix the MD040
lint errors for the blocks referenced (the blocks around the "これから: <質問の要点>..."
example and the other two fenced blocks in that section).
In `@codex/.codex/skills/cursor-do/SKILL.md`:
- Around line 23-29: Update the fenced code blocks in SKILL.md that currently
use backticks without a language to specify the language as text; locate the
blocks containing the snippet that starts with "🚀 cursor / composer-2.5-fast /
feat/foo-bar / Add login form validation" and the other two fenced blocks around
the lines noted (the ones matching the MD040 warnings) and change their opening
fences from ``` to ```text so the mirror matches the original and resolves the
MD040 lint warnings.
In `@opencode/skills/breezing/SKILL.md`:
- Around line 18-24: The three fenced code blocks in SKILL.md lack language
specifiers (triggering markdownlint MD040); update each triple-backtick block
shown in the diff examples to include a language token (e.g., change ``` to
```text) so all three code fences in SKILL.md are annotated and the MD040
warnings are resolved.
In `@opencode/skills/cursor-ask/SKILL.md`:
- Around line 35-38: The markdown contains bare fenced code blocks (e.g., the
block showing "🚀 cursor / composer-2.5-fast / ask" and the other example
blocks) that trigger MD040; update each triple-backtick fence to include a
language tag such as ```text (or a more appropriate language) so they become
fenced code blocks with a language specifier and stop CI noise; search for the
three backtick blocks in SKILL.md (the example blocks around the
cursor/composer-2.5-fast/ask snippets) and replace ``` with ```text (or another
suitable tag) consistently.
In `@opencode/skills/cursor-do/SKILL.md`:
- Around line 18-24: The Markdown in SKILL.md uses untagged fenced code blocks
for the narration examples which triggers MD040; update each affected fenced
block (the three narration/example blocks currently surrounded by ``` ... ```)
to include an explicit language tag such as ```text so the code fences become
```text ... ```; locate the three example/narration code fences in SKILL.md (the
blocks around the "🚀 cursor / composer-2.5-fast ..." example and the two other
similar blocks) and add the language tag to each opening fence.
In `@skills/breezing/SKILL.md`:
- Around line 32-38: The fenced code blocks in SKILL.md are missing language
specifiers (causing MD040); update each triple-backtick block shown in the diff
to include an explicit language like ```text (or a more specific language if
appropriate) — fix the block at the snippet shown and the other affected blocks
(the ones around the later ranges mentioned) and re-run markdownlint to confirm
the MD040 warning is resolved.
In `@skills/cursor-ask/SKILL.md`:
- Around line 40-43: The markdown has fenced code blocks without a language
specifier (triggering MD040); update the three code fences shown in SKILL.md
(the block under the "🚀 cursor / composer-2.5-fast / ask" example and the other
two similar blocks later) to use an explicit language tag by replacing the
leading "```" with "```text" so each code block starts with "```text" and the
rest remains unchanged.
In `@skills/cursor-do/SKILL.md`:
- Around line 23-29: The markdown has fenced code blocks without a language
specifier (MD040); update each offending triple-backtick block that contains the
snippets like "🚀 cursor / composer-2.5-fast / feat/foo-bar / Add login form
validation" and the other two blocks in this file to include a language token
(e.g., ```text) immediately after the opening backticks so the code fences
become ```text … ```; ensure you update all occurrences referenced in the diff
(the three fenced blocks) so they pass MD040 validation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 35efac6e-4b4c-42a2-9a59-7e3777ec47f4
📒 Files selected for processing (9)
CHANGELOG.mdcodex/.codex/skills/cursor-ask/SKILL.mdcodex/.codex/skills/cursor-do/SKILL.mdopencode/skills/breezing/SKILL.mdopencode/skills/cursor-ask/SKILL.mdopencode/skills/cursor-do/SKILL.mdskills/breezing/SKILL.mdskills/cursor-ask/SKILL.mdskills/cursor-do/SKILL.md
| ### Changed | ||
|
|
||
| - **`/breezing` / `/cursor:ask` / `/cursor:do` の起動ナレーションを「計画明示型」に緩和**: v4.13.2 で導入した Narration Rules が「最初の text は 1 行のみ・中間ナレーション一切禁止」と振り切れすぎ、起動後に何も表示されず「今から何をするのか分からない」状態だった。3 skill の Narration Rules を「**起動時に banner + 実行計画 (2-4 step、合計 5 行以内) を明示してから実行開始**」に書き換え、見やすい進捗報告 (各ステップの 1 行ステータス・判断に必要な中間結果・1 行の経緯) を明示的に許可。禁止対象は **冗長さ** (同じ事実の 2 回言い換え / 中身のない前置き / 3 行以上の経緯振り返り / 起動シーケンス中の ★ Insight ブロック) のみに限定。 | ||
|
|
||
| - 今まで: `🚀 cursor / composer-2.5-fast / ask` の 1 行だけ出して即委譲。ユーザーは進行中の処理が見えず不安。 | ||
| - 今後: banner の直後に「これから: backend resolve → composer に diff レビュー委譲 → verdict 要約」のような実行計画を添え、各ステップ完了を 1 行で報告する。冗長な繰り返しだけを避ける。 | ||
|
|
There was a problem hiding this comment.
Before/After テーブルを追加してください。
今回の変更は影響範囲が広いので、[Unreleased] の当該エントリにも Before/After テーブルを入れておくと、差分意図が一目で追える状態になります。
As per coding guidelines, CHANGELOG.md: Keep CHANGELOG in Keep a Changelog format; include Before/After tables for major changes.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 9 - 15, The CHANGELOG entry under "### Changed"
describing the Narration Rules change for `/breezing` / `/cursor:ask` /
`/cursor:do` needs a Before/After table added (and mirrored in the
`[Unreleased]` section) so readers can quickly see the behavioral delta; update
the relevant entry text for v4.13.2 (the paragraph referencing
"起動ナレーションを「計画明示型」に緩和" and the bullet examples) by inserting a concise two-column
Before / After table that shows the previous behavior ("1-line banner only, no
intermediate narration, immediate delegation") versus the new behavior ("banner
+ 2–4 step execution plan, per-step 1-line status reports, allow minimal
intermediate results, block only verbose repetition/Insight blocks"), and ensure
the `[Unreleased]` heading contains the same Before/After table for this change.
| ``` | ||
| × 「cursor に質問を投げる準備をします」→ bash → 「投げます」 | ||
| × 「ask モードは読み取り専用なので安全です」と再説明 | ||
| 🚀 cursor / composer-2.5-fast / ask | ||
| これから: <質問の要点> を composer に投げて、結果を 3-5 行で要約 | ||
| ``` |
There was a problem hiding this comment.
ミラーファイル側もコードフェンスの言語指定を追加してください。
Line 40 / Line 60 / Line 67 の fenced code block が MD040 違反です。元ファイルと同じく ```text 等を付けて揃えてください。
Also applies to: 60-64, 67-70
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 40-40: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@codex/.codex/skills/cursor-ask/SKILL.md` around lines 40 - 43, The fenced
code blocks in SKILL.md (the blocks shown around the "🚀 cursor /
composer-2.5-fast / ask" example and the other examples at the same section) are
missing a language identifier and violate MD040; update each triple-backtick
fence (the blocks currently like ``` ) to include a language label (e.g.,
```text) so they match the original/mirror file and fix the MD040 lint errors
for the blocks referenced (the blocks around the "これから: <質問の要点>..." example and
the other two fenced blocks in that section).
| ``` | ||
| × 「composer 2.5 で実装する流れですね、まず確認します」 | ||
| × 「Cursor を呼ぶ前に branch を見ます」 → bash → 「branch を確認しました」 | ||
| 🚀 cursor / composer-2.5-fast / feat/foo-bar / Add login form validation | ||
| これから: | ||
| 1. pre-check (branch / cursor-agent) → 専用 worktree 作成 | ||
| 2. composer に実装委譲 (--write) | ||
| 3. diff レビュー → cherry-pick → Plans.md 更新 | ||
| ``` |
There was a problem hiding this comment.
codex ミラーにも fenced code block の言語指定を入れてください。
Line 23 / Line 47 / Line 54 は MD040 警告対象です。```text を付けて本体側と一致させてください。
Also applies to: 47-51, 54-57
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 23-23: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@codex/.codex/skills/cursor-do/SKILL.md` around lines 23 - 29, Update the
fenced code blocks in SKILL.md that currently use backticks without a language
to specify the language as text; locate the blocks containing the snippet that
starts with "🚀 cursor / composer-2.5-fast / feat/foo-bar / Add login form
validation" and the other two fenced blocks around the lines noted (the ones
matching the MD040 warnings) and change their opening fences from ``` to ```text
so the mirror matches the original and resolves the MD040 lint warnings.
| ``` | ||
| 🚀 cursor / composer-2.5-fast / feat/hah-11-golden-rule-lint / Reviewer | ||
| これから: | ||
| 1. backend/model を resolve | ||
| 2. composer に diff レビューを委譲 (read-only) | ||
| 3. verdict を 3-5 行で要約 → Plans.md 更新 | ||
| ``` |
There was a problem hiding this comment.
コードフェンスに言語指定を付けてください（MD040）。
3箇所の fenced code block に言語が未指定で、markdownlint 警告が出ています。text などを付けて lint をクリーンにしてください。
差分例
-```
+```text
🚀 cursor / composer-2.5-fast / feat/hah-11-golden-rule-lint / Reviewer
これから:
1. backend/model を resolve
2. composer に diff レビューを委譲 (read-only)
3. verdict を 3-5 行で要約 → Plans.md 更新- +text
× 「composer 2.5 使うモード」= cursor backend で Composer に委託、ですね（と解釈の言い換え）
× 「前回 Reviewer が止まったので別系統に逃がすのは理にかなっています」（3 行以上の振り返り）
× 「使い方を確認します」 → bash → 「呼べます」（中身のない前置き + 同じ事実の 2 回言い換え）
-```
+```text
🚀 cursor / composer-2.5-fast / feat/hah-11-golden-rule-lint / Reviewer
これから: backend resolve → composer に diff レビュー委譲 (read-only) → verdict 要約
</details>
Also applies to: 42-46, 49-52
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.22.1)</summary>
[warning] 18-18: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @opencode/skills/breezing/SKILL.md around lines 18 - 24, The three fenced
code blocks in SKILL.md lack language specifiers (triggering markdownlint
MD040); update each triple-backtick block shown in the diff examples to include
a language token (e.g., change totext) so all three code fences in
SKILL.md are annotated and the MD040 warnings are resolved.
</details>
<!-- fingerprinting:phantom:triton:hawk -->
<!-- This is an auto-generated comment by CodeRabbit -->
| ``` | ||
| × 「cursor に質問を投げる準備をします」→ bash → 「投げます」 | ||
| × 「ask モードは読み取り専用なので安全です」と再説明 | ||
| 🚀 cursor / composer-2.5-fast / ask | ||
| これから: <質問の要点> を composer に投げて、結果を 3-5 行で要約 | ||
| ``` |
There was a problem hiding this comment.
fenced code block に言語タグを付けてください。
Line 35 / Line 55 / Line 62 のコードフェンスが MD040 違反です。```text（または適切な言語）に統一すると CI ノイズを防げます。
Also applies to: 55-59, 62-65
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 35-35: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@opencode/skills/cursor-ask/SKILL.md` around lines 35 - 38, The markdown
contains bare fenced code blocks (e.g., the block showing "🚀 cursor /
composer-2.5-fast / ask" and the other example blocks) that trigger MD040;
update each triple-backtick fence to include a language tag such as ```text (or
a more appropriate language) so they become fenced code blocks with a language
specifier and stop CI noise; search for the three backtick blocks in SKILL.md
(the example blocks around the cursor/composer-2.5-fast/ask snippets) and
replace ``` with ```text (or another suitable tag) consistently.
| ``` | ||
| × 「composer 2.5 で実装する流れですね、まず確認します」 | ||
| × 「Cursor を呼ぶ前に branch を見ます」 → bash → 「branch を確認しました」 | ||
| 🚀 cursor / composer-2.5-fast / feat/foo-bar / Add login form validation | ||
| これから: | ||
| 1. pre-check (branch / cursor-agent) → 専用 worktree 作成 | ||
| 2. composer に実装委譲 (--write) | ||
| 3. diff レビュー → cherry-pick → Plans.md 更新 | ||
| ``` |
There was a problem hiding this comment.
Narration 例示ブロックに言語タグが必要です。
Line 18 / Line 42 / Line 49 のコードフェンスが MD040 で警告されています。```text を明示してください。
Also applies to: 42-46, 49-52
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 18-18: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@opencode/skills/cursor-do/SKILL.md` around lines 18 - 24, The Markdown in
SKILL.md uses untagged fenced code blocks for the narration examples which
triggers MD040; update each affected fenced block (the three narration/example
blocks currently surrounded by ``` ... ```) to include an explicit language tag
such as ```text so the code fences become ```text ... ```; locate the three
example/narration code fences in SKILL.md (the blocks around the "🚀 cursor /
composer-2.5-fast ..." example and the two other similar blocks) and add the
language tag to each opening fence.
| ``` | ||
| 🚀 cursor / composer-2.5-fast / feat/hah-11-golden-rule-lint / Reviewer | ||
| これから: | ||
| 1. backend/model を resolve | ||
| 2. composer に diff レビューを委譲 (read-only) | ||
| 3. verdict を 3-5 行で要約 → Plans.md 更新 | ||
| ``` |
There was a problem hiding this comment.
コードフェンスに言語指定を追加してください。
markdownlint の MD040 指摘どおり、これらの fenced code block は言語未指定です。```text などを付けて lint を通してください。
Also applies to: 56-60, 63-66
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 32-32: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/breezing/SKILL.md` around lines 32 - 38, The fenced code blocks in
SKILL.md are missing language specifiers (causing MD040); update each
triple-backtick block shown in the diff to include an explicit language like
```text (or a more specific language if appropriate) — fix the block at the
snippet shown and the other affected blocks (the ones around the later ranges
mentioned) and re-run markdownlint to confirm the MD040 warning is resolved.
| ``` | ||
| × 「cursor に質問を投げる準備をします」→ bash → 「投げます」 | ||
| × 「ask モードは読み取り専用なので安全です」と再説明 | ||
| 🚀 cursor / composer-2.5-fast / ask | ||
| これから: <質問の要点> を composer に投げて、結果を 3-5 行で要約 | ||
| ``` |
There was a problem hiding this comment.
コードブロックの言語指定が不足しています。
Line 40 / Line 60 / Line 67 の fenced code block に言語がなく、MD040 に引っかかります。```text を付与してください。
Also applies to: 60-64, 67-70
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 40-40: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/cursor-ask/SKILL.md` around lines 40 - 43, The markdown has fenced
code blocks without a language specifier (triggering MD040); update the three
code fences shown in SKILL.md (the block under the "🚀 cursor /
composer-2.5-fast / ask" example and the other two similar blocks later) to use
an explicit language tag by replacing the leading "```" with "```text" so each
code block starts with "```text" and the rest remains unchanged.
| ``` | ||
| × 「composer 2.5 で実装する流れですね、まず確認します」 | ||
| × 「Cursor を呼ぶ前に branch を見ます」 → bash → 「branch を確認しました」 | ||
| 🚀 cursor / composer-2.5-fast / feat/foo-bar / Add login form validation | ||
| これから: | ||
| 1. pre-check (branch / cursor-agent) → 専用 worktree 作成 | ||
| 2. composer に実装委譲 (--write) | ||
| 3. diff レビュー → cherry-pick → Plans.md 更新 | ||
| ``` |
There was a problem hiding this comment.
コードフェンスの言語未指定を修正してください。
Line 23 / Line 47 / Line 54 の fenced code block が MD040 違反です。```text などを追加してください。
Also applies to: 47-51, 54-57
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 23-23: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@skills/cursor-do/SKILL.md` around lines 23 - 29, The markdown has fenced code
blocks without a language specifier (MD040); update each offending
triple-backtick block that contains the snippets like "🚀 cursor /
composer-2.5-fast / feat/foo-bar / Add login form validation" and the other two
blocks in this file to include a language token (e.g., ```text) immediately
after the opening backticks so the code fences become ```text … ```; ensure you
update all occurrences referenced in the diff (the three fenced blocks) so they
pass MD040 validation.
harness-review minor finding 対応: cursor-ask Step 1 が「最初の text は 1 行だけ」のままで Step 0 の banner+plan と seam があった。cursor-do と 同形の reconciliation 文を追加し、Step 1 は banner 確認の役割と明示。 cursor-do Step 1 header を "first text echo (1 行…)" から "banner + plan を出し切る" に rename し、multi-line plan を出す実態に整合。 mirror (opencode / codex) 同期、validate-plugin + check-consistency 全合格。 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Promote [Unreleased] to [4.13.3] - 2026-06-01 and bump all version surfaces from 4.13.2 to 4.13.3 (patch). - Cursor 初回利用の摩擦 4 点を解消 (Chachamaru127#193, Chachamaru127#194) - breezing 起動ナレーションを計画明示型に緩和 (Chachamaru127#190) - WorktreeCreate hook の出力修正 (Chachamaru127#188, lands Chachamaru127#168) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 participant
Summary
v4.13.2 で入れた Narration Rules が振り切れすぎて「起動後に何も表示されず、今から何をするのか分からない」状態だった。3 skill (
breezing/cursor-ask/cursor-do) の Narration Rules を 計画明示型 に緩和する。Before / After
禁止対象は 冗長さ だけに限定:
起動時の出力例 (After)
Files
skills/breezing/SKILL.md— Narration Rules 書き換え + Fast Path / Reviewer-only flow を banner+plan に整合skills/cursor-ask/SKILL.md— Narration Rules + Step 0/1 を banner+plan にskills/cursor-do/SKILL.md— Step 0 NARRATION RULES + Step 1 の「echo 以外 text 禁止」を計画明示と整合opencode/skills/*,codex/.codex/skills/*同期CHANGELOG.md[Unreleased] に Changed entryTest plan
bash tests/validate-plugin.sh— 101/101 PASS (sandoff)bash scripts/ci/check-consistency.sh— 全合格 (mirror drift 0)🤖 Generated with Claude Code
Summary by CodeRabbit
改善
/breezing、/cursor:ask、/cursor:doの起動時にバナー＋実行計画（合計最大5行、各スキルで想定行数を明確化）を即時表示するようになりましたドキュメント