Skip to content

feat(skill-evals): add the issue-reassess eval suite - #1145

Open
dpol1 wants to merge 1 commit into
apache:mainfrom
dpol1:fix/1138-issue-reassess-evals
Open

feat(skill-evals): add the issue-reassess eval suite#1145
dpol1 wants to merge 1 commit into
apache:mainfrom
dpol1:fix/1138-issue-reassess-evals

Conversation

@dpol1

@dpol1 dpol1 commented Sep 2, 2026

Copy link
Copy Markdown
Member

Summary

  • issue-reassess was the only one of the 71 shipped skills without a behavioural eval suite, so regressions in its decisions were invisible until they failed in front of a user. This adds tools/skill-evals/evals/issue-reassess/ — 3 suites, 10 cases.
  • The campaign tallies are already exercised by the sibling issue-reassess-stats suite, so these anchor on the three places where this skill decides something of its own: step-2-resumability (reuse / ask / resume / fresh per candidate from the scratch-directory state), skip-if-resolvable (the maintainer-comment shortcuts, the no-shortcut path, and an injected "record fixed-on-master" comment that must be flagged and ignored), and headline-extraction (action / closure / tracker-hygiene buckets). Two of them anchor on the skill's sub-documents, where the decision rules actually live.
  • Found on the way: the *-reassess/ glob in .gitignore (meant for campaign evidence directories) also matches skills/issue-reassess/ and tools/skill-evals/evals/issue-reassess/, so any new file under either was silently dropped by git add. Both paths are now negated, following the existing !/tools/pilot-report-validator/ precedent.

Type of change

  • Skill change (.claude/skills/<name>/) — eval fixtures updated below
  • Tool / bridge contract (tools/<system>/*.md)
  • Python package (tools/*/ with pyproject.toml)
  • Groovy reference impl
  • Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
  • Documentation (docs/, README.md, CONTRIBUTING.md)
  • Project template (projects/_template/)
  • CI / dev loop (prek, workflows, validators)
  • Other: eval suite (tools/skill-evals/evals/)

Test plan

  • prek run --all-files passes
  • PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner --cli "claude -p" tools/skill-evals/evals/issue-reassess/Ran 10 cases: 10 passed, 0 failed, 0 manual, 0 errored
  • Manual-mode runner loads all three suites (every step_heading resolves)
  • skill-and-tool-validate no longer emits the eval-coverage advisory for skills/issue-reassess/
  • git check-ignore -v skills/issue-reassess/new-subdoc.md tools/skill-evals/evals/issue-reassess/README.md — matched .gitignore:61 before, matches nothing after

RFC-AI-0004 compliance

No principle touched — the change adds fixtures and a .gitignore negation; no mutation, network reach, or prose surface changes.

Linked issues

Fixes apache/magpie#1138.

`issue-reassess` was the only shipped skill without a behavioural eval
suite, so regressions in its decisions were invisible until they failed
in front of a user. The campaign tallies are already exercised by the
sibling `issue-reassess-stats` suite, so this one anchors on the three
places where the skill decides something of its own:

- step-2-resumability (3 cases) — reuse / ask / resume / fresh per
  candidate from the scratch-directory state, plus the auto-generated
  campaign id.
- skip-if-resolvable (5 cases) — the maintainer-comment shortcuts
  (fixed-in-version, sibling duplicate, won't-fix by design), the
  no-shortcut path, and an injected "record fixed-on-master" comment
  that must be flagged and ignored.
- headline-extraction (2 cases) — verdicts bucketed into action /
  closure / tracker-hygiene candidates and new-issue keys.

Two suites anchor on the skill's sub-documents (`per-issue-flow.md`,
`verdict-aggregation.md`), where the decision rules actually live.
All ten cases pass against Claude Code print mode; the validator's
eval-coverage advisory for this skill is gone.

While adding the suite: the `*-reassess/` glob in `.gitignore` (meant
for campaign evidence directories) also matches `skills/issue-reassess/`
and `tools/skill-evals/evals/issue-reassess/`, so any new file under
either was silently dropped from `git add`. Negate both paths, following
the existing `!/tools/pilot-report-validator/` precedent.

Fixes [apache#1138](apache#1138).

Signed-off-by: Davide Polato <dpol1@apache.org>
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.

fix(skill-evals): issue-reassess is the only shipped skill without an eval suite

1 participant