sync-context

Synchronize project documentation files with the actual codebase state.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/sandrusidoltst-a11y/fit_pal --skill sync-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-context
Source: https://github.com/sandrusidoltst-a11y/fit_pal/tree/main/.claude/skills/sync-context
Command: npx skills add https://github.com/sandrusidoltst-a11y/fit_pal --skill sync-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that project documentation, including CLAUDE.md, PRD.md, and the skill catalog in .claude/skills/, accurately reflects the current state of the codebase and project requirements.

Core Features & Use Cases

  • Documentation Auditing: Compares documented state against the actual project structure, skills, and PRD implementation.
  • Gap Identification: Pinpoints discrepancies between documentation and reality, such as missing skills, outdated paths, or PRD drift.
  • Automated Updates: Modifies documentation files (CLAUDE.md, PRD.md, skill files) to align with the codebase.
  • Use Case: After refactoring the agent's core logic or adding a new tool, use this Skill to automatically update the project's central documentation to reflect these changes, preventing outdated information.

Quick Start

Run the sync context skill to update the project documentation.

Frequently Asked Questions about sync-context

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

FAQPage Schema
How do I keep my project documentation in sync with my codebase?

To keep project documentation in sync with your codebase, this skill scans current files like CLAUDE.md and PRD.md, analyzes the actual project structure, identifies discrepancies, and automatically updates relevant documentation to match the code.

How do I update a PRD document after refactoring code?

Updating a PRD document after refactoring code involves scanning the current implementation status, identifying PRD drift where requirements no longer match reality, and modifying PRD.md to accurately reflect the new architectural patterns and project state.

What is the best way to audit project documentation for outdated paths and missing skills?

Auditing project documentation for outdated paths and missing skills requires comparing the documented state against the actual project structure and skill catalog in .claude/skills/, pinpointing gaps, and flagging discrepancies for automated updates.

Can I automatically sync skill references in .claude/skills/ with my current project structure?

Yes, you can automatically sync skill references by scanning the .claude/skills/ directory, analyzing the active project structure, and modifying the skill files to ensure all documented skill references, MCP servers, and architectural patterns are accurate.

When should I run a documentation sync for my project management files?

You should run a documentation sync whenever you add a new tool, refactor core agent logic, or alter the project structure, ensuring your project management files and codebase documentation never become outdated or misleading.