curate-cluster

Reconcile project documentation and script indices against the current file system state.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill curate-cluster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curate-cluster
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/curate-cluster
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill curate-cluster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of index drift and repository bloat by automatically reconciling documentation and scripts with the project index, while preventing the accidental commitment of active build artifacts or work-in-progress code.

Core Features & Use Cases

  • Index Reconciliation: Automatically detects unreferenced files, dangling references, and count mismatches between the disk and the project index.
  • Concurrency-Safe Commits: Uses a liveness heuristic to exclude actively-built code lanes from commits, ensuring you never snapshot a peer's half-written work.
  • Artifact Management: Automatically identifies and ignores build artifacts to keep the repository clean and history lean.

Quick Start

Run the curate-cluster skill to reconcile the project index and commit only the quiescent documentation and tooling changes.

Frequently Asked Questions about curate-cluster

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

FAQPage Schema
How do I prevent committing active build artifacts and work-in-progress code to a git repository?

Concurrency-safe repository maintenance prevents committing active build artifacts by using a liveness heuristic to stage only quiescent file paths. It surveys disk contents and excludes actively-built code lanes to avoid snapshotting incomplete work.

What is the best way to reconcile project documentation indices against the current file system state?

Index reconciliation automatically detects unreferenced files, dangling references, and count mismatches between the disk and the project index. It updates index metadata to ensure documentation and script indices match current file system state.

Do I need specific tools or environments to run automated repository gardening tasks?

Automated repository gardening requires standard git CLI tools and a shell environment to perform idempotent repository maintenance. No additional dependencies are needed beyond these standard command-line utilities.

Why does index drift occur in project repositories and how can it be fixed?

Index drift occurs when documentation and script indices fall out of sync with the file system. Automated reconciliation surveys disk contents, updates index metadata, and stages only quiescent paths to correct drift and prevent repository bloat.

When should I avoid using automated concurrency-safe git commits?

Avoid automated concurrency-safe commits when working outside a standard shell environment or lacking git CLI tools. The skill relies on disk surveys and liveness heuristics, which may not suit environments without standard command-line access.