lesson-reviewer

Automating lesson review involves scanning daily GitHub issue submissions, routing each entry to the correct skill reference, updating documentation, and closing the issue. This workflow ensures field-submitted lessons are systematically curated and incorporated into maintainable references.

Routing field-submitted knowledge requires evaluating each lesson entry against existing skill references, matching it to the appropriate core rule, and applying local edits to the corresponding documentation files. This maintains proper categorization and ensures lessons remain discoverable for future users.

Yes, managing lesson curation relies on GitHub CLI workflows to scan submissions from issues labeled lesson-learned. The CLI facilitates the triage process and enables the automated closure of issues once the local documentation edits are successfully incorporated.

Yes, you can propagate learned lessons by integrating field-submitted notes into existing skill reference files. The workflow prepares updates for the relevant references, applies the local edits, and closes the originating GitHub issue to maintain documentation quality and discoverability.

A key limitation of GitHub issues for knowledge management is that curation requires local edits to reference files after routing. The workflow cannot automatically generate new skill categories, meaning lessons must map to pre-existing skill references or core rules to be successfully incorporated and closed.