Write and reconcile xmris dev-diary entries documenting implementation decisions.
npx skills add https://github.com/andrewendlinger/xmris --skill dev-diary
Please help me install this Agent Skill. Skill: dev-diary Source: https://github.com/andrewendlinger/xmris/tree/main/.claude/skills/dev-diary Command: npx skills add https://github.com/andrewendlinger/xmris --skill dev-diary
This Skill helps you document important implementation decisions in xmris before and after they are built, so contributors can review the reasoning behind a change without reading the whole plan or diff.
Write a dev-diary entry for this xmris change, then ask me whether to publish it now or skip it.
High-intent search queries and answers about installing and using this skill.
To document implementation decisions for a multi-PR refactor, write a dev-diary entry explaining why the change was made and how it ended up. This provides a reviewable record of the reasoning without requiring contributors to read the entire diff.
A two-pass decision record workflow drafts an entry at the start of a change as a review gate, then reconciles it at the end to match the merged code. This preserves the reasoning behind the change while removing pending assumptions once the implementation is real.
Write a decision record when a change involves real decision weight, such as choosing between viable approaches, adding new conceptual surface, or coordinating multi-PR refactors. This ensures the tradeoffs and reasoning are preserved for future review.
Keep markdown documentation concise by writing a short dev-diary entry that captures the story without explaining the whole plan. Include assumptions while work is pending, and remove them once the implementation is complete and the final pass is reconciled.
Yes, the dev diary workflow requires a rendered first-pass draft before implementation. This draft acts as a review gate to evaluate the reasoning, followed by a reconciled final pass that aligns with the merged code and removes pending assumptions.
arthur-debertGenerate a feature specification covering context, goals, risks, and testing.
FuZhiyuRefactor project changes into a consistent, minimal, reviewable diff.
FelipePepeEnforce JSDoc/TSDoc comments and ADR updates in PRs.
GustavoGutierrezWrite Markdown Architecture Decision Records with append-only supersession and required alternatives.
