Skip to content

playbooks: repo-sweep next records every skill as run when an entry does not apply #5181

Description

@kyle-sexton

Problem

reference/next.md section 2 reads an entry's applies-when but never tells the session to test it before invoking the entry's skills. When an entry does not apply, the only way to close it is tick.sh <id> no-findings <skill@version>..., which takes every skill in the entry.

Observed on melodic-software/.github PR #153, step file-names (playbooks 0.13.0, docs-hygiene 0.23.1):

  • applies-when is "repo has a docs tree and a file-name casing rule". The repo has no docs/ tree; inventory.sh printed SCANNED 0 docs.
  • docs-hygiene:realign-file-names was never invoked, yet the checklist now reads docs-hygiene:audit-file-names@0.23.1, docs-hygiene:realign-file-names@0.23.1, no findings.
  • history.sh derives run / rerun recommendations from these records, so a later plan treats realign as having run at 0.23.1.
  • "Ran and found nothing" and "did not apply" produce the same line; nothing distinguishes them.

Proposed fix

  1. In next.md section 2, test applies-when with cheap evidence (tracked-file listing, globs) before invoking any skill.
  2. Add tick.sh <id> not-applicable <reason>, which records no skill versions, and teach history.sh to treat it as not run.
  3. When an entry stops partway (audit found nothing, fix skill not needed), record only the skills actually invoked.

Acceptance

  • A not-applicable entry is ticked without invoking its skills and without Playbook-Step or version claims.
  • history.sh does not count a not-applicable tick as a run.

🤖 Generated with Claude Code

https://claude.ai/code/session_01S5b57FoPJkJMe1BDwhExiG

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: lowNice-to-have, cosmetic, or speculative; opportunistic.work-class: mechanicalDeterministic, trivially reversible maintenance: dependency bumps, lint/format, sync.

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions