Lfe Archivist

Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.

44 stars 3 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add StChiotis/Library-First-Engineering --skill lfe-archivist
Manual install
git clone --depth 1 https://github.com/StChiotis/Library-First-Engineering.git /tmp/Library-First-Engineering
mkdir -p ~/.claude/skills
cp -r /tmp/Library-First-Engineering/.agents/skills/lfe-archivist ~/.claude/skills/lfe-archivist

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# LFE Archivist

## Mission
Keep the project's documentation and history perfectly in sync with the codebase. You are the "Guardian of Truth" who ensures the Library System remains reliable.

## Sub-Pipeline (execute in this order)
1. `/lfe-archivist` (this skill) → Sync docs, update CHANGELOG, update pipeline_status.md
2. Check: More slices? → Yes: loop back to Architect for next slice. No: proceed to cleanup.
3. Cleanup → Archive/delete coordination files from `.plans/`
4. Check: Hygiene due? (5+ sessions since last sweep) → If yes, recommend `/lfe-hygiene`

## Toolbox
- `/lfe-to-issues`: Use to create follow-up issues for deferred work or technical debt.

## Hard Rules
1. **Library System Hierarchy**: Maintain the three-layer documentation structure (Entrance Card → Floor Map → Shelf Index).
2. **CHANGELOG Rolling Window (HARD)**: keep `CHANGELOG.md` at 7 milestones or fewer; move the oldest to an archive file.
3. **Index Sync**: Every ADR or documentation change requires updating the relevant index tables.
4. **No Behavior Changes**: You only touch documentation and planning artifacts.
5. **File-Based Input**: Read `.plans/inspection_report.md` as input. The Inspector's report tells you what passed.
Read the full skill on GitHub

Details

Skill name
lfe-archivist
Path
.agents/skills/lfe-archivist/SKILL.md
License
MIT
Repo updated
14 July 2026

FAQ

What does the Lfe Archivist skill do?

Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.

How do I install the Lfe Archivist skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add StChiotis/Library-First-Engineering --skill lfe-archivist. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Lfe Archivist popular?

It lives in StChiotis/Library-First-Engineering, which has 44 GitHub stars and 3 forks.

Related skills

Lfe Architect

44

StChiotis/Library-First-Engineering

Act as the Architect for an LFE-compliant project. Design solutions and draft high-fidelity plans.

Other

Lfe Boot

44

StChiotis/Library-First-Engineering

Bootstrap an LFE-compliant session. Reads orientation docs, checks for interrupted sessions, and activates the project persona. Use at the start of any session.

Writing & Content

Lfe Builder

44

StChiotis/Library-First-Engineering

Act as the Builder for an LFE-compliant project. Use when implementing an approved plan, writing code in src/**, or running unit tests.

Testing & QA

Issue Tree Builder

33

AnugamChakra/think-like-a-strategy-consultant

Builds a MECE issue tree that breaks a business problem into clean, non-overlapping, fully-covering branches drilled deep enough to reach testable hypotheses. Use this skill whenever the user wants to decompose or break down a problem, asks "build me an issue tree", "is this MECE", "map out the possible causes", "what are all the drivers of X", or is staring at a big messy problem and needs structure. Trigger it for both diagnostic problems (why did something happen) and solution problems (how could we achieve a goal). Use it even when the user doesn't say "issue tree" — if they need to struct

Git & Code Review

Runtime Lifecycle

43

rohitg00/agentbrain

Use when verification depends on agent runtime phases, queued input, tool-call lifecycle, save points, retry, abort, compaction, or branch behavior.

Git & Code Review

Video Project Github

38

vargHQ/skills

Keep an AI video project, or any agent-built project, in a private GitHub repo, even when the person has never used git. The agent does everything: creates the private repo, keeps keys out, saves a version after every approved step, stores big video and audio outside git so GitHub's 100 MB limit never hits, and restores the whole project byte for byte on a new laptop. Sets up the folder layout for mood boards, script, sound, characters, blockout, shots and the edit as text (HyperFrames, Remotion, ffmpeg), records the prompt, model, seed and cost of every take, and gives an undo for anything. U

Git & Code ReviewIn 1 list

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.