Skip to content

fix(fix-plan): resolve full list-item block before toggling a sync marker - #378

Draft
daegunjhy wants to merge 1 commit into
next-featfrom
fix/fix-plan-sync-nested-child
Draft

fix(fix-plan): resolve full list-item block before toggling a sync marker#378
daegunjhy wants to merge 1 commit into
next-featfrom
fix/fix-plan-sync-nested-child

Conversation

@daegunjhy

Copy link
Copy Markdown
Contributor

Summary

  • During a /fix-plan --deep sync pass, an item was located by grepping a unique substring on its top-level - [ ] line and toggled to [x] without reading a directly-nested - [ ] sub-bullet immediately below it -- that sub-bullet carried its own independent PR reference and was left unresolved even though it had also already merged.
  • sync.md had no explicit instruction to treat a nested sub-bullet as its own completion unit, and no instruction that batch-query results must be applied to every extracted number rather than a hand-picked subset.

Changes

  • skills/fix-plan/sync.md: add a "List-item block boundary" step (with Don't/Do) to step 1 (Extract), and a new prohibition row to the Sync-specific prohibitions table.

Test plan

  • bash scripts/lint-frontmatter.sh -- pre-existing unrelated failures only (resources/scripts/tests subdirs missing SKILL.md, confirmed present on next-feat baseline before this change)
  • pytest tests -- 103 passed, 4 skipped (pre-push hook, full run)
  • bash tests/ (bats) -- passed (pre-push hook)
  • Reviewer: confirm the new Don't/Do table reads clearly against sync.md's existing style

…rker

sync.md's marker-toggle procedure only ever located an item by grepping
a unique substring on its top-level line, so a nested `  - ` sub-bullet
carrying its own independent marker and PR/Issue reference could be left
unresolved after the parent was checked off. It also let the batch-query
step's results be applied to a hand-picked subset of the extracted
numbers instead of every one of them.

Add a list-item block boundary step to Extract (step 1) plus two
prohibition rows to the Sync-specific prohibitions table.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants