checking-freshness

Check documentation freshness by comparing source file modifications against the corresponding SKILL.md and references using git log. This automated detection flags stale documentation whenever source code changes occur, ensuring docs stay aligned with the actual codebase.

Yes, you can detect stale documentation before committing by integrating a pre-commit hook. This hook runs an automated freshness check that warns you about outdated SKILL.md and references content during the git commit process, preventing documentation from falling behind code changes.

Documentation freshness checking is the process of identifying when documentation becomes stale relative to source changes. It works by using git log to determine the last modification times of source files and skill docs, then comparing them to surface outdated content that needs updating.

Yes, the freshness check applies to core source directories including packages/core and server/web along with their associated references. It maps these source files against SKILL.md and references to identify drift between code and documentation across your project structure.

The best way to keep SKILL.md files in sync is to automate detection of outdated documentation by comparing source changes with the corresponding skill docs. Using a pre-commit hook to warn about stale content ensures documentation updates happen alongside code changes rather than as an afterthought.

Your pre-commit hook warns about outdated documentation because it runs an automated freshness check comparing source file modification times against SKILL.md and references. This warning indicates that your documentation has fallen behind recent code changes and needs to be updated before committing.