Archive stale and superseded solution documentation with YAML frontmatter analysis.
npx skills add https://github.com/lenlla/one_shot_build --skill prune-knowledge
Please help me install this Agent Skill. Skill: prune-knowledge Source: https://github.com/lenlla/one_shot_build/tree/main/skills/prune-knowledge Command: npx skills add https://github.com/lenlla/one_shot_build --skill prune-knowledge
Review and clean up solution documentation to remove staleness, contradictions, superseded content, and duplicates across project and team knowledge stores while preserving history by archiving rather than deleting.
Run the prune-knowledge skill to scan project and shared solution docs, archive superseded items, flag stale or incompatible entries, detect duplicates, and stage commits for human review.
High-intent search queries and answers about installing and using this skill.
To archive stale and superseded solution documentation, this skill scans project and team knowledge stores, extracts YAML frontmatter, and moves outdated files to a category-specific _archived folder. It preserves history by archiving rather than deleting, then stages git commits for human review.
Detecting duplicate solution docs across project and team knowledge bases is handled by scanning configured directories and comparing YAML frontmatter metadata. The skill flags duplicate candidates for merge or supersession, generating a summary report of potential redundancies for review.
Flagging outdated documentation based on last_validated dates and version constraints involves comparing extracted YAML frontmatter against configurable thresholds and project tool constraints. The skill identifies incompatible entries and produces a pruning summary detailing deprecated or stale files.
Automating quarterly knowledge base cleanup and staging changes as git commits is supported during periodic maintenance or project onboarding. The skill archives superseded items, flags stale entries, detects duplicates, and stages git commits to record archival, deprecation, and refresh actions for review.
YAML frontmatter in solution docs is required to perform knowledge base pruning, as the skill extracts these metadata fields to compare last_validated dates and version constraints. Without frontmatter, staleness detection and version incompatibility checks cannot be executed.
You should run a documentation pruning workflow on your shared knowledge path during periodic maintenance, quarterly cleanups, or project onboarding. This ensures solution docs remain current, organized, and free of contradictions or superseded content across both project and team stores.
jaredpalmerDocument solved problems into categorized YAML-frontmatter docs under docs/solutions.
smallorbitSynchronize a local Git workspace with the remote develop branch.
aget-frameworkValidate knowledge base structure, frontmatter compliance, and content freshness.
smallorbitIdentify and remove stale files, outdated documentation, and cruft from a codebase.
