reindex-docs

Reindex PDF and HTML documents and update index.html with a rebuilt documentTree.

Updated Jan 8, 2026

Search Tags:#documentation #HTML #Git #PDF #documentTree #reindex #index.html

Ready to run

npx skills add https://github.com/alanben/ClaudeSkills --skill reindex-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reindex-docs
Source: https://github.com/alanben/ClaudeSkills/tree/main/reindex-docs
Command: npx skills add https://github.com/alanben/ClaudeSkills --skill reindex-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious task of keeping a repository's document index current by reindexing PDFs and HTML files and updating index.html.

Core Features & Use Cases

Scan the repository for all PDFs and HTML files using Glob patterns (**/.pdf, **/.html) and run searches in parallel for efficiency.
Read the existing index.html to understand its structure and the documentTree object.
Update index.html with a new last-updated date, rebuild the documentTree with a Client → Project → Section → Folder hierarchy, and sort documents in reverse chronological order.
Commit and push changes following the repository's conventions and messaging guidelines.

Quick Start

Run the reindex-docs skill to scan for PDFs and HTMLs, update index.html, and push changes.

Frequently Asked Questions about reindex-docs

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

FAQPage Schema

How do I automatically reindex PDF and HTML documents in a Git repository?▼

To automatically reindex PDF and HTML documents, you can run a skill that scans your repository using Glob patterns, rebuilds the documentTree into a Client → Project → Section → Folder hierarchy, and commits the refreshed index.html automatically.

What is the best way to keep my document index updated when files change frequently?▼

Keeping your document index updated is handled by reindexing all PDFs and HTML files, sorting them in reverse chronological order, and updating the last-updated date in index.html to reflect the most recent changes.

How does reindexing organize files in the documentTree hierarchy?▼

Reindexing organizes files in the documentTree by structuring them under a Client → Project → Section → Folder hierarchy and listing all discovered documents in reverse chronological order based on their updates.

Can I reindex documents in repositories without an existing index.html file?▼

Reindexing requires an existing index.html file because the process reads its current structure and documentTree object to update the last-updated date and rebuild relative paths accurately.

Does the reindexing process automatically commit and push changes to Git?▼

Yes, the reindexing process commits and pushes changes to Git by following the repository's specific messaging guidelines and conventions after updating index.html and rebuilding the documentTree.

What types of documents are supported when rebuilding a repository index?▼

Rebuilding a repository index supports PDF and HTML documents, scanning for them using parallel Glob patterns like **/*.pdf and **/*.html to ensure all relevant files are included in the updated documentTree.