gpd-compact-state

Archive historical entries from STATE.md to STATE-ARCHIVE.md when exceeding a line limit.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-compact-state-chargrnmn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-compact-state
Source: https://github.com/CharGrnmn/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-compact-state
Command: npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-compact-state-chargrnmn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill maintains the readability and manageability of the project's documentation by compacting the STATE.md file when it exceeds a certain line limit.

Core Features & Use Cases

  • Automatic Compaction: Automatically archives historical entries from STATE.md to STATE-ARCHIVE.md when the file size exceeds a specified threshold.
  • Selective Archiving: Identifies and archives completed phases, old decisions, and resolved issues to keep the active context lean.
  • Data Integrity: Ensures that the compacted STATE.md file retains all required sections and cross-references remain valid.
  • Manual Trigger: Can be manually triggered to compact the file without waiting for automatic triggers.
  • Use Case: Ideal for maintaining project documentation in research projects, software development, and any scenario where a project grows over time and requires efficient management of documentation.

Quick Start

Run the gpd-compact-state skill to automatically compact the STATE.md file when it exceeds the line limit.

Frequently Asked Questions about gpd-compact-state

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

FAQPage Schema
How do I compact a project STATE.md file when documentation gets too long?▼

This Skill automates compacting project documentation by archiving historical entries from STATE.md to STATE-ARCHIVE.md, ensuring the active context remains concise once the file exceeds a specified line threshold.

What is the best way to archive completed project phases from active documentation?▼

Archiving completed project phases is handled through selective archiving, which identifies old decisions and resolved issues, moving them to a separate archive file to keep the active STATE.md context lean.

Does compacting STATE.md break internal cross-references or remove required sections?▼

No, compacting STATE.md maintains data integrity by ensuring the compacted file retains all required sections and that cross-references remain valid after historical entries are archived.

Can I manually trigger project documentation compaction before the automatic line limit is reached?▼

Yes, you can manually trigger documentation compaction to archive historical entries and compact the STATE.md file immediately without waiting for the automatic file size threshold to be exceeded.

When should I use automated state management for project documentation?▼

Automated state management is ideal for research projects, software development, and any scenario where a project grows over time and requires efficient management of historical and current documentation data.