justinmclean opened a new pull request, #509:
URL: https://github.com/apache/airflow-steward/pull/509

   ## Summary
   
   Adds the `issue-stale-sweep` general-issue triage skill, closing the 
stale-handling gap noted in the triage-mode spec Known Gaps. The skill sweeps 
open issues dormant past configurable warn/close/hard-close thresholds, 
classifies each as REQUEST-UPDATE or CLOSE-STALE, drafts a comment for each 
candidate, and posts only after per-item maintainer confirmation. CLOSE-STALE 
items require a mandatory two-step confirmation before the issue is actually 
closed. Security-signal issues are skipped and surfaced for private routing. 
Comes with the stale-sweep-config.md template, symlinks, capability-map entry, 
and 22-case eval suite.
   
   ## Type of change
   
   <!-- Tick all that apply. -->
   
   - [X] 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:
   
   ## Test plan
   
   - [X] `prek run --all-files` passes
   - [ ] For Python packages touched: `uv run pytest` / `ruff check` / `mypy` 
passes
   - [ ] For Groovy bridges touched: command-line invocation tested end-to-end
   - [X] For skill changes: eval suite passes for the affected skill
         (`PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner 
tools/skill-evals/evals/<skill>/`)
   - [ ] For skill *behaviour* changes: a new or updated eval fixture is 
included in this PR
         (a regression test for the bug fixed / the behaviour added — see 
CONTRIBUTING.md)
   - [ ] Other:
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to