issue-doc-sync

To sync closed GitHub issues into repository docs, this skill incrementally processes only issues updated since the last run and creates or merges docs under the appropriate lifecycle directories.

Incremental issue synchronization uses a persisted state cache to track updatedAt timestamps, ensuring only newly closed or modified issues are processed while skipping unchanged ones.

Yes, issue sync records skip, merge, and new-doc decisions to a persistent state cache, providing full traceability for how each closed GitHub issue was integrated into the docs.

Keeping project documentation updated with closed issues without reprocessing everything requires an incremental sync approach that checks issue updatedAt timestamps against a state cache to process only recent changes.

GitHub issue to docs sync requires the existence of a stable workflow and can reference scripts, review processes, and state tracking to ensure reproducible results across runs.

Issue documentation sync skips closed GitHub issues that have not been updated since the last successful run, logging the skip decision in the state cache to avoid redundant doc generation.