lfe-archivist

Synchronize LFE documentation with the codebase after commit approval.

43|2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-archivist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfe-archivist
Source: https://github.com/StChiotis/Library-First-Engineering/tree/main/.agents/skills/lfe-archivist
Command: npx skills add https://github.com/StChiotis/Library-First-Engineering --skill lfe-archivist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The LFE Archivist Skill helps in maintaining synchronization between a project's documentation and codebase by providing documentation sync, CHANGELOG updates, and pipeline status cleanup post-approval.

Core Features & Use Cases

  • Documentation Synchronization: Ensures that project documentation stays up-to-date with the codebase.
  • CHANGELOG Management: Manages the CHANGELOG, adhering to a rolling window policy.
  • Pipeline Status Cleanup: Cleans up planning and coordination files to reflect completed work.
  • Use Case: After a new code commit has been reviewed and approved, this skill would be used to sync documentation, update the CHANGELOG, and prepare for the next stage in the software development process.

Quick Start

To update documentation after an approved change, execute /lfe-archivist within the LFE project context.

Frequently Asked Questions about lfe-archivist

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

FAQPage Schema
How do I synchronize project documentation with my codebase after a commit approval?

To synchronize project documentation with your codebase after commit approval, you can use a documentation archivist skill to update CHANGELOG entries, synchronize pipeline status, and clean up temporary workflow files.

What is the best way to manage CHANGELOG entries using a rolling window policy?

Managing CHANGELOG entries with a rolling window policy involves automatically updating the changelog to reflect recent approved changes while maintaining a concise, navigable project history without retaining obsolete logs indefinitely.

How do I clean up temporary planning files after completing a workflow phase?

Cleaning up temporary planning files after completing a workflow phase requires a pipeline status cleanup process that removes obsolete coordination files, ensuring the repository reflects only completed work and active tasks.

When do I need to update pipeline_status in my software development workflow?

You need to update pipeline_status in your software development workflow immediately after a new code commit has been reviewed and approved, ensuring the project's documentation and status tracking remain synchronized.

Does the LFE archivist workflow require any dependencies to run?

The LFE archivist workflow operates without external dependencies, relying solely on its internal scripts to execute documentation synchronization, CHANGELOG management, and pipeline cleanup tasks within the project context.

Why does my project documentation lose synchronization with the codebase after updates?

Project documentation loses synchronization with the codebase when post-commit cleanup and changelog updates are not automated, requiring an archivist process to enforce documentation sync and maintain accurate project history.