evo-archiving
Archiving Changes
Overview
After implementation is complete and verified, archive the changes by updating project documentation. This ensures future AI sessions have accurate context about the codebase.
Announce at start: "I'm using the evo-archiving skill to document the changes."
Triggering Scenarios
This skill is triggered in two scenarios with different context sources:
| Scenario | Context Source | How to Gather Changes |
|---|---|---|
| After evo-executing-plans | Plan + implementation | Read the plan file, cross-reference with actual changes made |
| After manual changes | Git diff + conversation | Use git diff and git status to identify changes, ask user for intent if unclear |
The Process
More from rockcookies/skills
node-dev
Modern JavaScript/TypeScript runtime development conventions and tooling. Use when setting up JS/TS projects with Node, Bun, or Deno, configuring ESLint, pnpm workspaces, monorepos, library publishing, or npm package development.
18tsdown
Bundle TypeScript and JavaScript libraries with blazing-fast speed powered by Rolldown. Use when building libraries, generating type declarations, bundling for multiple formats, or migrating from tsup.
17web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
17frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
15git-master
>
15turborepo
|
14