update-redirects

Automating documentation redirects involves scanning your git history for moved files and applying rules to a redirects.jsonc file. This skill adds and updates redirect entries automatically, ensuring internal links remain stable and unbroken after repository restructuring.

Detecting broken targets and circular references in redirects.jsonc requires a validation routine that checks redirect mappings. This skill validates all redirect entries, identifies orphaned paths, and provides cleanup suggestions to eliminate loops and dead links across your documentation.

Yes, you can preserve comments in redirects.jsonc during batch operations. This skill maintains the existing redirects.jsonc formatting and comments while applying bulk redirect updates across large documentation suites.

Scanning git history to propose new redirects involves analyzing past file moves and renames. This skill scans your documentation repositories to detect relocated files and suggests the necessary redirect entries to maintain navigational path stability.

Redirect validation for link stability is needed because section reorganizations often leave orphaned entries or broken targets. This skill enforces the redirects file format and integrates with link-check workflows to ensure users and internal links don't break.