Analyze merged PR diffs and issue STM evidence to write learning proposals.
npx skills add https://github.com/kapilvirenahuja/garura --skill distill-kapilvirenahuja
Please help me install this Agent Skill. Skill: distill Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/plays/distill Command: npx skills add https://github.com/kapilvirenahuja/garura --skill distill-kapilvirenahuja
It turns merged PR diffs plus any available issue STM evidence into lightweight, staged learning proposals without blocking or halting the ship workflow.
Run distill after merge-pr to stage learning proposals to issue STM at the distill evidence path when evidence.record is enabled.
High-intent search queries and answers about installing and using this skill.
To extract post-merge learnings from a git diff into STM, analyze merged PR diffs alongside available issue STM evidence. This distillation process generates lightweight learning proposals and stages them safely without halting your workflow.
Yes, you can automate learning extraction from merged PRs without blocking the ship workflow using a fire-and-forget approach. It catches and logs any failures gracefully, ensuring the calling ship play proceeds to scenario validation without ship-halting exceptions.
Post-merge learning distillation handles trivial PR diffs by safely skipping them. It analyzes the diff and produces no proposals for trivial changes, returning a completed result with no_learnings instead of staging unnecessary data.
Post-merge learning proposals are staged exclusively in the issue STM at the path {stm_base}/{issue}/evidence/distill/. The process writes a proposals.yaml file to this directory and intentionally avoids writing to product LTM.
Yes, you need FAST-mode invocation of knowledge-extractor to distill PR diffs. This mode is required to process the merged PR diffs and relevant STM evidence to produce 1–2 learning proposals efficiently.
The best way to stage ship-after-merge learning proposals for non-trivial PRs is to run a distill operation after merge-pr. This fits ship-after-merge scenarios perfectly when evidence recording is enabled, generating staged proposals without halting.
lhpaulAutomate local post-merge cleanup and issue tracker updates.
kapilvirenahujaAnalyze merged PR diffs and issue STM evidence to generate up to two staged proposals.yaml entries.
kapilvirenahujaCommit feature branch work, open a pull request, and merge to main.
kapilvirenahujaPromote approved taxonomy-tagged issue proposals into product LTM and ADR archives.
