reindex

Trigger reindexing of a specific WordPress extension. Use to rebuild the search index for a plugin, theme, or core version.

12 stars

Best use case

reindex is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Trigger reindexing of a specific WordPress extension. Use to rebuild the search index for a plugin, theme, or core version.

Teams using reindex 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

$curl -o ~/.claude/skills/reindex/SKILL.md --create-dirs "https://raw.githubusercontent.com/PeterBooker/veloria/main/.claude/skills/reindex/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/reindex/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How reindex Compares

Feature / AgentreindexStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Trigger reindexing of a specific WordPress extension. Use to rebuild the search index for a plugin, theme, or core version.

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 Extension

Trigger reindexing of a specific WordPress plugin, theme, or core version.

## Usage

- `/reindex plugins akismet` - Reindex the Akismet plugin
- `/reindex themes flavor` - Reindex the flavor theme
- `/reindex cores 6.7.1` - Reindex WordPress core 6.7.1

## Steps

1. **Parse arguments**
   - `$REPO`: Repository type (`plugins`, `themes`, or `cores`)
   - `$SLUG`: Extension slug (or version for cores)
   - Both are required

2. **Ensure binary is current**
   ```bash
   go install ./...
   ```

3. **Check if the server is running**
   ```bash
   curl -s http://localhost:8585/up 2>&1
   ```

4. **If server is running**, trigger reindex via API:
   ```bash
   curl -s -X POST "http://localhost:8585/api/reindex/$REPO/$SLUG" 2>&1
   ```

5. **If server is not running**, use the index CLI directly:
   - First, determine the zip URL for the extension
   - Then run:
     ```bash
     veloria index --repo=$REPO --slug=$SLUG --zipurl="$ZIP_URL" 2>&1
     ```

6. **Report results**
   ```
   ## Reindex Results

   - Extension: $REPO/$SLUG
   - Method: API / CLI
   - Status: success / failed
   - Details: [output from command]
   ```

## CLI vs API

| Method | When | Notes |
|--------|------|-------|
| API (`/api/reindex`) | Server running | Handles zip URL lookup, DB update, and hot-swap |
| CLI (`veloria index`) | Server not running | Requires explicit `--zipurl`, no DB update |

The API method is preferred as it handles the full pipeline including database updates and live index hot-swap.

Related Skills

test

12
from PeterBooker/veloria

Run Go unit tests. Use after code changes to verify correctness.

security-scan

12
from PeterBooker/veloria

Run gosec and govulncheck to find security vulnerabilities. Use before releases or after dependency changes.

race-check

12
from PeterBooker/veloria

Run Go race detector to find data races in concurrent code. Use after any change to mutexes, goroutines, or channels.

profile

12
from PeterBooker/veloria

Run CPU and memory profiling with pprof to identify performance hotspots. Use when investigating high resource usage.

migrate

12
from PeterBooker/veloria

Create and manage database migrations using goose. Use for schema changes, new tables, or index optimization.

lint

12
from PeterBooker/veloria

Run golangci-lint and static analysis on Go code. Use before pushing or to check code quality.

integration-test

12
from PeterBooker/veloria

Run integration tests that require Docker (Postgres, MinIO via testcontainers). Use to validate database and storage behavior.

generate

12
from PeterBooker/veloria

Run go generate to build templ templates and frontend assets. Use after changing templates or CSS/JS.

deps

12
from PeterBooker/veloria

Check and tidy Go module dependencies. Use after adding/removing imports or before releases.

coverage

12
from PeterBooker/veloria

Run tests with coverage analysis and identify untested code paths. Use to find gaps before releases.

check

12
from PeterBooker/veloria

Run pre-push quality checks (vet + lint + tests with race detector). Use before pushing code.

benchmark

12
from PeterBooker/veloria

Run Go benchmarks and compare results to detect performance regressions. Use before and after performance-related changes.