Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

knowledge: docpage-digest correction rounds have no convergence rule or round cap

Open Beginner friendly
  • Is something wrong?
#7,282 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start with plugins/knowledge/skills/docpage-digest/context/dual-verification.md, especially the correction-round rules around lines 46–78. Read how corrections are recorded and how new findings carry forward, then add the suggested convergence rule and a three-round cap with open findings and round history sent to the interview handoff. Done when the rules explain both how to avoid repeated paraphrase findings and what happens after the cap.

Written by the indexing model from the issue text.

Description

priority: low

Summary

/knowledge:docpage-digest's dual-verification rules define how a correction round is recorded, but not when rounds stop or how a correction should be worded so the next re-verify does not raise a new finding against the fix itself. On pages whose rules carry per-event exceptions, rounds can repeat without converging.

Affected area / component

plugins/knowledge/skills/docpage-digest/context/dual-verification.md

Steps to reproduce

  1. Digest a page whose prose restates rules with per-event exceptions, for example https://code.claude.com/docs/en/hooks#exit-code-output and https://code.claude.com/docs/en/hooks#block-the-action-when-a-hook-fails.
  2. Let a re-verify flag a dropped exception in a unit's Summary or Implications, and correct it by adding scope wording.
  3. Re-verify. A different exception is now missing from the new wording. Repeat.

Expected behavior

The skill states a convergence rule for corrections and a round cap, after which open findings move to the interview handoff with their round history.

Actual behavior

  • context/dual-verification.md:46-51 defines one corrections file per unit per round and a per-round index; :66-72 requires an applied record whose "New findings" feed the next round; :74-78 requires each round to sweep every fixed class twice. Nothing bounds the number of rounds or says how to word a correction.
  • Observed on the hooks page: one unit needed four correction rounds. Rounds 1 to 3 each rewrote a conditional rule (exit code 2, onFailure, timeouts) in Summary/Implications prose with new scope wording, and each re-verify found that the new wording dropped a different exception. Round 4 converged only after the run added its own rule: replace paraphrase of a conditional rule with a neutral sentence that points at the claim labels.

Suggested fix

Add to dual-verification.md:

  • a convergence rule: a correction removes paraphrase of a conditional rule and points at the claim labels, rather than adding scope wording;
  • a round cap (for example three rounds), after which open findings go to the interview handoff with the round history.

Environment

knowledge plugin 0.21.1 (line numbers from main on 2026-10-12).

Found during the upstream-pointer sweep (PRs #7061-#7274).

Dominant language
Shell
Stars
22
Forks
2
Avg merge
7h 42m
Merged PRs (30d)
923

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.