Kaku Maintainer Sweep

Use this skill for maintenance work that spans GitHub issues, pull requests, local fixes, main CI, and public follow-up. It is not the notarized release flow, and it must not contain private signing credentials or local machine setup.

Workflow

1. Refresh live state

   • Run gh issue list --state open --limit 20 and gh pr list --state open --limit 20.
   • For each actionable item, read gh issue view <n> or gh pr view <n> and confirm title, author, state, body, and recent comments.
   • If the task asks for the latest state, refresh the lists again before final decisions.

2. Map reports to code

   • Find the latest release tag with git tag --sort=-version:refname | head -1; ignore rolling tags such as nightly unless the maintainer asks about them.
   • Compare relevant changes with git log <tag>..HEAD --oneline, git show, and targeted rg.
   • Do not treat a closed issue as proof. Identify the fix mechanism, the commit, or the remaining gap.