ito-archive
Finalizes changes by integrating them into the codebase and updating specifications.
Install
mkdir -p .claude/skills/ito-archive && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18889" && unzip -o skill.zip -d .claude/skills/ito-archive && rm skill.zipInstalls to .claude/skills/ito-archive
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Archive a completed change and update main specifications. Use when the user has finished implementing and wants to integrate the change into the main codebase.Key capabilities
- →Archive a completed change
- →Update main specifications with accepted delta-specs
- →Capture design rationale for future reference
- →Report archive location and schema
- →Refresh wiki topic/index/status material
- →Preserve locked worktrees
How it works
The skill archives a completed change by promoting accepted delta-specs to the main project specification and capturing design rationale. It then reports the archive details and refreshes relevant wiki materials.
Inputs & outputs
When to use ito-archive
- →Archive finished implementation
- →Update project specs
- →Capture design memory
About this skill
Archive lifecycle
Require explicit user confirmation before archive. Determine the full change ID, reverify the integrated result, and render the source of truth:
ito agent instruction archive --change "<change-id>"
Follow its spec promotion and archive sequence exactly. ito-archive owns accepted delta-spec promotion; there is no separate archive-change or sync-specs skill. Report the archive location, schema, promoted specs, verification evidence, and any change with no delta specs.
After success, refresh relevant .ito/wiki/ topic/index/status material when useful and capture durable lessons through the configured provider:
ito agent instruction memory-capture --context "<decision and rationale>"
Use the finish/cleanup instruction for branch and worktree follow-through. Preserve locked worktrees, require typed confirmation before destructive discard, and never force-push implicitly. Wiki or memory follow-through is recommended and must not hide an archive failure.
<!-- ITO:END -->When not to use it
- →When the user has not finished implementing the change
- →When the change is not ready to be integrated into the main codebase
Limitations
- →Requires explicit user confirmation before archiving
- →Does not force-push implicitly
- →Does not hide an archive failure with wiki or memory follow-through
How it compares
This workflow automates the promotion of delta-specs and captures design memory as part of the archival process, which is more structured than a manual archival.
Compared to similar skills
ito-archive side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ito-archive (this skill) | 0 | 13d | Review | Intermediate |
| deepwiki-rs | 25 | 9mo | Review | Intermediate |
| repo-research-analyst | 1 | 6mo | Review | Intermediate |
| c4-component | 1 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by withakay
View all by withakay →You might also like
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
repo-research-analyst
parcadei
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase
c4-component
sickn33
Expert C4 Component-level documentation specialist. Synthesizes C4 Code-level documentation into Component-level architecture, defining component boundaries, interfaces, and relationships. Creates component diagrams and documentation. Use when synthesizing code-level documentation into logical components.
agent-pseudocode
ruvnet
Agent skill for pseudocode - invoke with $agent-pseudocode
spec
matteocervelli
>
cs-arch
wildlily1021
维护 `codestable/architecture/` 这份只记现状的系统地图，三种模式 update / check / backfill。触发：用户说"刷新 architecture"、"做架构检查"、"补这个模块的架构文档"、"方案和代码对得上吗"，或 feature 阶段需要先做架构动作。不写未来规划（走 cs-roadmap）。