summary

Detect documentation drift in the PetCare project against canonical references and memory indices.

1|Updated Sep 9, 2025
One-click install
npx skills add https://github.com/davidting0918/PetCare --skill summary-davidting0918
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: summary
Source: https://github.com/davidting0918/PetCare/tree/main/.claude/skills/summary
Command: npx skills add https://github.com/davidting0918/PetCare --skill summary-davidting0918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Summary skill detects drift between the PetCare repository's current documentation and its canonical references (CLAUDE.md, all related SKILL.md files, and memory indices), and suggests per-file fixes to re-synchronize the docs after user confirmation.

Core Features & Use Cases

  • Drift detection across CLAUDE.md, the /summary SKILL.md, and memory indices to surface inconsistencies.
  • Per-file diff proposals with conservative changes that only apply after explicit user confirmation, compatible with auto-mode or manual usage.
  • Guided workflow for memory and documentation alignment to keep project docs in sync during ongoing work.

Quick Start

Scan for drift and propose fixes, then confirm which diffs to apply.

Frequently Asked Questions about summary

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

FAQPage Schema
How do I detect documentation drift in project docs?

Documentation drift occurs when project docs fall out of sync with canonical references like CLAUDE.md and memory indices. It surfaces as outdated instructions or missing context, which drift detection addresses by proposing per-file diffs to re-synchronize the documentation.

How do I align CLAUDE.md and project documentation after updates?

To fix documentation drift, scan the repository to compare current docs against CLAUDE.md and memory indices. The skill generates per-file diff proposals for re-synchronization, applying changes conservatively only after explicit user confirmation in either auto or manual mode.

Can I apply documentation diffs automatically without manual review?

No, diff proposals are never applied automatically without explicit confirmation. The skill requires explicit user confirmation before applying any per-file diffs to re-synchronize docs, ensuring conservative changes whether using auto-mode or manual usage.

Does the drift detection process modify source code or configuration files?

No, the drift detection process does not touch source code or non-doc configuration files. It strictly ensures no code is modified, proposing conservative per-file diffs exclusively for documentation alignment after explicit user confirmation.

What's the best way to keep memory indices and version-controlled docs in sync?

The best way to keep memory indices and version-controlled docs in sync is through guided drift detection. It compares current documentation against canonical references and memory indices, then proposes per-file diffs to align project docs after explicit user confirmation.