Append phase completion details and final summaries to changelog.md files.
npx skills add https://github.com/eveld/claude --skill update-changelog-eveld
Please help me install this Agent Skill. Skill: update-changelog Source: https://github.com/eveld/claude/tree/main/skills/update-changelog Command: npx skills add https://github.com/eveld/claude --skill update-changelog-eveld
Append phase tracking or final summary to changelog.md during implementation.
Use the skill after each implementation phase to update thought documents with a phase entry in changelog.md and after completion to append a final summary.
High-intent search queries and answers about installing and using this skill.
You can automate changelog updates by appending phase completion details after each implementation phase. This records what was done versus planned, deviations, changed files, and discoveries into a standardized changelog.md file.
A final summary section in a changelog should summarize key deviations, document lessons learned, and note technical debt or follow-up work. It is appended after all project phases are completed to provide closure.
To track deviations and files changed during development, append a phase tracking entry to your changelog.md. This entry documents what was actually done against the plan, reasons for deviations, and a list of modified files.
The expected file path format for project changelogs follows a standardized structure under thoughts/NNNN-description/changelog.md. Consistent paths ensure phase updates and final summaries are tracked correctly.
Yes, you need standardized Phase Update Format and Final Summary Format templates. These templates ensure consistent recording of phase details and project completion summaries within your changelog.md file.
You should update your changelog during workflows immediately after completing each implementation phase, and once at project completion. This ensures progress tracking and discoveries are captured accurately as they happen.
product-on-purposeInitialize JPKB projects with standardized documentation and folder structure.
BrennonTWilliamsScan project directories to identify bugs and generate structured issue files.
corticalstackValidate implementation plans against code changes and verification outcomes.
vuralserhat86Enforce JSDoc/TSDoc, inline comments, Keep a Changelog, and Conventional Commits standards.
