Skip to content

[refactor] Sync diagnosis-detection narrowing to sister skills idd-all/idd-list/idd-update (verify follow-up from #53) #59

@kiki830621

Description

@kiki830621

Problem

From verification of #53 (PR #58):
「Sister substring scans 仍存在 — idd-all/SKILL.md:441,524 (Python substring), idd-list/SKILL.md:115, idd-update/SKILL.md:120## Diagnosis 做 phase 推斷,同樣 false-positive 風險」
— Source: team:regression + codex

#53 narrow fix 只動 idd-all-chain/SKILL.md。Sister skill 仍有同類 false-positive risk:

  • plugins/issue-driven-dev/skills/idd-all/SKILL.md:441 — Python substring if "## Diagnosis" in comment_body
  • plugins/issue-driven-dev/skills/idd-all/SKILL.md:524 — same pattern
  • plugins/issue-driven-dev/skills/idd-list/SKILL.md:115掃 comments 的標題推斷(prose-level,但底層可能 substring)
  • plugins/issue-driven-dev/skills/idd-update/SKILL.md:120 — 同 pattern

#53 Implementation Plan 已 explicit 列為 out-of-scope。本 issue 追蹤是否同步 narrow fix。

Type

refactor (sync narrowing across sister skills)

Priority

P3 (none observed in real-world chain runs to date)

Strategy

For each location:

  1. idd-all/SKILL.md:441,524: Python substring → equivalent line-start check (regex ^## Diagnosis on per-comment body)
  2. idd-list/SKILL.md:115 + idd-update/SKILL.md:120: 釐清是 prose-only heuristic 還是有底層 jq/grep。若有具體 filter,sync narrow

Acceptance

Related

Source: surfaced during /idd-verify --pr 58 (cluster #49 #53), Step 5b triage. Master report: #58 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions