code-gardening

Detect and fix drift in codebases by updating durable docs and state.

3|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/prateek/dotfiles --skill code-gardening
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-gardening
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/code-gardening
Command: npx skills add https://github.com/prateek/dotfiles --skill code-gardening

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code Gardening keeps touched codebases trustworthy by surfacing drift, aligning intent, and updating durable state across docs, tests, and configs.

Core Features & Use Cases

  • Detects misalignment between code, tests, docs, and agent guidance.
  • Proposes durable-state updates to restore coherent provenance.
  • Scopes drift correction to the relevant durable resources (AGENTS.md, README, SKILL.md, CLAUDE.md, etc.)

Quick Start

Describe drift in a repository and propose durable-state updates to restore alignment.

Frequently Asked Questions about code-gardening

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

FAQPage Schema
How do I fix documentation drift in a codebase?

Fix documentation drift by detecting misalignment between code, tests, and durable docs like AGENTS.md or README, then proposing durable-state updates to restore coherent provenance and intent across the repository.

What is durable state in code repositories?

Durable state in code repositories refers to persistent files like AGENTS.md, CLAUDE.md, README, and SKILL.md that capture intent and provenance, requiring synchronization to maintain alignment with touched code.

How do I sync AGENTS.md and CLAUDE.md with code changes?

Sync AGENTS.md and CLAUDE.md by scoping drift correction to relevant durable resources, enforcing validation of frontmatter and parser outputs, and capturing updates in the nearest durable docs to restore alignment.

Does code gardening work with build and config docs?

Yes, code gardening works with build and config docs by detecting misalignment, redefining intent and provenance, and enforcing validation of frontmatter, parser outputs, and state-sync requirements to update durable state.

When should I update durable state files in my repository?

Update durable state files when touched codebases show drift, misalignment between code and docs, or invalidated frontmatter and parser outputs, ensuring updates are captured in the nearest durable resources.