hiivmind-corpus-refresh

Refresh and sync a local corpus index with upstream documentation sources.

1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiivmind-corpus-refresh
Source: https://github.com/hiivmind/hiivmind-corpus/tree/main/skills/hiivmind-corpus-refresh
Command: npx skills add https://github.com/hiivmind/hiivmind-corpus --skill hiivmind-corpus-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a unified, repeatable mechanism to refresh and synchronize a corpus index with upstream documentation sources, ensuring your local corpus stays current.

Core Features & Use Cases

  • Per-source freshness checks to identify which sources have updates and require re-indexing.
  • Two-mode operation: report status or perform updates with optional auto-approve for CI.
  • Index and metadata updates to reflect refreshed sources, including last_updated_at, last_indexed_at, and commit SHAs.

Quick Start

Run a corpus refresh to sync the index with upstream sources for the current project.

Frequently Asked Questions about hiivmind-corpus-refresh

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

FAQPage Schema
How do I refresh and sync a corpus index with upstream documentation sources?

To refresh a corpus index, trigger a sync request to compare local index freshness against upstream sources. The process identifies changed sources and updates index metadata, commit SHAs, and timestamps to keep documentation current.

How do I check which documentation sources need re-indexing before running a full update?

Check documentation source freshness by running a status report mode operation. This performs per-source freshness checks to identify exactly which upstream sources have updates and require re-indexing, without applying any changes.

Can I automate corpus index refreshes in a CI pipeline?

Yes, you can automate corpus index refreshes in CI by using the update operation mode with optional auto-approval enabled. This allows the refresh process to run without manual intervention to keep documentation current.

What do I need to set up before refreshing a local corpus index?

Before refreshing a corpus index, you need a valid config.yaml file and an existing local index. These prerequisites ensure the refresh process can accurately compare and synchronize with the upstream sources.

Does running a corpus refresh update embeddings alongside the index metadata?

Yes, running a full corpus refresh updates optional embeddings workflows if they are configured in your setup. Alongside embeddings, it updates per-source freshness data, last_indexed_at timestamps, and commit SHAs.

What is the best way to keep local documentation indexes current with upstream changes?

The best way to keep documentation indexes current is a unified refresh mechanism that syncs the local corpus with upstream sources in one step. It updates per-source freshness data and metadata to reflect the latest changes.