reindex-docs
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
Best use case
reindex-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
Teams using reindex-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/reindex-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How reindex-docs Compares
| Feature / Agent | reindex-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Reindex Documents Skill
You are a specialized agent for maintaining the document index in this static document repository.
## Your Task
Re-index all PDF and HTML documents in the repository and update index.html, then commit and push the changes.
## Process Steps
1. **Scan for all documents**
- Use Glob to find all PDF files: `**/*.pdf`
- Use Glob to find all HTML files: `**/*.html`
- Run these searches in parallel for efficiency
2. **Read current index.html**
- Read the existing index.html to understand the structure
- Note the current documentTree JavaScript object structure
3. **Update index.html with new documents**
- Update the `last-updated` date to today's date (format: YYYY-MM-DD)
- Update the `documentTree` object to include:
- All newly found documents
- Proper Client → Project → Section → Folder hierarchy
- Documents sorted in **reverse chronological order** (newest first)
- Clean, readable document titles
- Relative paths from root
4. **Organizational Rules**
- **Clients** (top level): Turnbuckle, Nextgen, Loeries, MachinaXX, etc.
- **Projects** (under clients): RentaStore, Adstream, LifeGauge, etc.
- **Sections** (under projects): Meeting notes, Technical, Projects, Programs, etc.
- **Folders** (under sections): Webstream, Phase 4, Modernization Program, etc.
- **Documents**: Individual PDF and HTML files
- Sort documents by date in reverse chronological order (most recent first)
- Remove any empty folders that have no documents
5. **Commit and Push**
- Add all untracked files (new documents)
- Commit index.html changes with descriptive message
- Commit new document files with descriptive message
- Push all commits to remote repository
- Use proper commit message format with Claude Code attribution
## Commit Message Format
Use this format for commits:
```
Update index with new documents - [Month Year]
Added/Updated documents:
- Client/Project: Document description
- Client/Project: Document description
Updated last modified date to YYYY-MM-DD
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
```
For new document files:
```
Add new client documents - [Month Year]
New documents added:
- Client/Project: Document description
- Client/Project: Document description
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
```
## Important Notes
- Exclude these HTML files from the document index (they are system files):
- `index.html` (the index itself)
- `repos.html` (repository index)
- `access-denied.html` (security page)
- Maintain the existing JavaScript structure and styling
- Preserve the auth.js script reference in the head section
- Keep sections collapsed by default for clean navigation
- Use relative paths for all document links
- Follow the existing naming conventions for document titles
## Expected Output
After completion, provide a summary of:
- Number of new documents added
- Number of clients/projects updated
- Commit IDs created
- Confirmation that changes were pushed successfullyRelated Skills
write-docs
Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.
wiki-docs
Document custom Magento 2 site functionality in the project wiki. Systematically captures custom features, modules, configurations, and business logic for client handover and developer onboarding.
update-docs
Update documentation pages to match source code changes on the current branch
update-docs-and-commit
Updates documentation files (changelog, architecture, project_status) based on git changes, then stages and commits all changes. Use after completing features or fixes.
three-tier-docs
Use after code changes. Syncs CLAUDE.md, CONTEXT.md, and docs/ai-context/ automatically.
sync-docs
Strategic documentation sync - review docs before implementation (pull context) OR export learnings after implementation (push to living docs). NOT bidirectional - two separate one-way operations at different phases.
smart-pr-docs
Intelligent PR documentation generator that analyzes code changes, tracks ripple effects across the codebase, updates claude.md files, and creates visual dependency maps. USE WITH codebase-architecture-mapper for elite "System-Aware" context.
review-docs
Review documentation (README.md and CLAUDE.md) for quality, completeness, and consistency. Use when asked to review docs, check documentation, validate README files, or audit CLAUDE.md coverage.
pitchdocs-suite
One-command generation and audit of the full public repository documentation set — README, CHANGELOG, ROADMAP, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, issue templates, PR template, and discussion templates. Use when setting up a new repo or auditing an existing one.
organize-agent-docs
Organize project agentic documentation into universal (AGENTS.md) and agent-specific files (CLAUDE.md, GEMINI.md, etc.). Use when asked to "organize agent docs", "separate agent instructions", "restructure AGENTS.md", or when a project has agent documentation that mixes universal and tool-specific content.
openclaw-docs-sync
Sync OpenClaw + ClawHub + Skills docs into a local mirror for the QMD memory backend.
moai-docs-unified
Enhanced docs unified with AI-powered features. Enhanced with Context7 MCP for up-to-date documentation.