issue-archive

Scan resolved issue files and archive them into a structured knowledge base.

2|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/cc-claws/cc-code --skill issue-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-archive
Source: https://github.com/cc-claws/cc-code/tree/main/.claude/skills/issue-archive
Command: npx skills add https://github.com/cc-claws/cc-code --skill issue-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you clean up resolved issues by moving finished work out of the active queue and turning it into durable project knowledge, so the repository stays organized and the same mistakes are less likely to repeat.

Core Features & Use Cases

  • Issue scanning and filtering: Detects which items in spec/issues/ are ready for archival based on their status.
  • Knowledge extraction: Summarizes each archived issue into domain-level lessons, keywords, and implementation takeaways.
  • Repository hygiene updates: Moves resolved issue files, adds archive markers, updates domain docs, refreshes global indexes, and links high-value lessons into CLAUDE.md.
  • Use case: A maintainer wants to clean up a backlog of Fixed and Closed issues while preserving the lessons learned for future debugging and planning.

Quick Start

Ask the assistant to archive all resolved issues in spec/issues/, extract reusable lessons, update the related domain files and CLAUDE.md links, and report the completed changes.

Frequently Asked Questions about issue-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive closed issues and extract reusable knowledge from a repository?

To archive closed issues, you scan resolved files in spec/issues/, filter them by status, extract domain-level lessons, move them to an archive, and update global indexes and CLAUDE.md with inline references.

How does issue archiving keep domain documentation and global indexes updated?

Issue archiving updates domain documentation by summarizing implementation takeaways, refreshing global indexes with de-duplicated entries, and linking high-value lessons directly into CLAUDE.md notes.

What is the best way to clean up a backlog of resolved repository issues while preserving lessons learned?

The best way to clean up resolved issues is applying deterministic status filtering to move finished files out of the active queue, extracting keywords, and adding archive markers to maintain repository hygiene.

Can I use issue archiving for long-term maintenance workflows with CLAUDE.md notes?

Yes, issue archiving is designed for long-term maintenance workflows, scanning resolved issue files and linking high-value lessons into CLAUDE.md notes to prevent repeating past mistakes.

How do I ensure de-duplicated index updates when archiving resolved issue files?

De-duplicated index updates are ensured by applying deterministic status filtering during the archival file move process, preventing redundant entries when refreshing the global index with extracted domain knowledge.

Why does issue archiving require deterministic status filtering for repository maintenance?

Deterministic status filtering is required to accurately detect which items in spec/issues/ are ready for archival, ensuring only resolved issues are processed for domain-level knowledge extraction and file moves.