docs(harness-config): drop the last /review:audit-enforceability reference from an eval sample

Open Beginner friendly
#12,762 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The only remaining hit is at line 7 of plugins/harness-config/evals/ag-grep-count-ceiling/samples/count-read-as-ceiling.json, so open that file and read the sample. Either repoint the reference to /corrections:codify or reword the line without review:audit-enforceability. Done when the issue's rg command over plugins and docs prints nothing.

Written by the indexing model from the issue text.

Description

agent-ready priority: medium status: ready work-class: scoped

Refs #7573

Outcome

The last stale reference to the removed /review:audit-enforceability skill is gone, so #7573's done-when grep prints nothing. On main the one hit is plugins/harness-config/evals/ag-grep-count-ceiling/samples/count-read-as-ceiling.json:7, added by #12052 after the absorb slice; point that sample at /corrections:codify or reword it without the old name.

Done when

The done-when line below is copied from #7573 as written.

  • rg -n 'review:audit-enforceability|retro codify' plugins docs --glob '!**/CHANGELOG.md' --glob '!.changes/**'
    prints nothing.

Notes

Drafted by the issue-triage session. Agent choice, not an owner answer. #7573's other criteria (check-skill, and the merged-PR and eval citations per slice) are checked on #7573 itself, not here.

Related

  • #7573 (parent), #12052.
Dominant language
Shell
Stars
22
Forks
2
Avg merge
1h 29m
Merged PRs (30d)
895

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.