What problem does it solve? Runtime issue logs written by notion-dev into client repos accumulate without any mechanism reading them, so feedback is either ignored or harvested selectively with no record of what was considered and rejected. This Skill reads every client log, forces every entry into an explicit disposition, applies the warranted fixes, and archives the evidence durably. ## Core Features & Use Cases - Eight-phase harvest pipeline: read prior harvests, collect and group signatures across clients, triage into five dispositions (apply, stale, decline, track, blocked), apply fixes, redact, archive, merge via pull request, and reset client logs. - Redaction gate: strips ticket content, emails, personal names, full database/page ids, absolute paths, and URLs from anything published to the public repo, generalizing to the kind or truncating ids. - Durable archive: writes docs/feedback/YYYY-MM-DD-harvest.md so occurrence counts, version ranges, and rejection rationales survive after client logs are reset. - Use Case: After several client teams run notion-dev and accumulate entries in .claude/notion-dev/notion-dev-issues.md, run the harvest to turn all of that feedback into one reviewed pull request plus a permanent archive, then clean the client logs. ## Quick Start Harvest the client feedback by reading the notion-dev issue logs from the paths in .claude/notion-dev/clients.txt, triaging every signature, and opening a single pull request with the fixes and archive.
