kb-batch

Run governed batch Knowledge Base operations with mandatory dry-run previews.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-batch
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/kb-batch
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky, one-off Knowledge Database changes by guiding you through controlled bulk operations with mandatory dry-run previews and governance checks.

Core Features & Use Cases

  • Mandatory dry-run: Shows exactly what will change before any updates are applied.
  • GOV-15 gate for defects/regressions: Requires owner approval confirmation for defect/regression work items.
  • 50-item maximum with validation: Rejects oversized batches and verifies all provided IDs exist before making changes.
  • Batch KB operations: Supports resolve-wis, promote-specs, and retire-specs to move records through governed lifecycle stages.

Real-world use case: you need to resolve a small set of work items and promote or retire related specs after an approved change, while keeping an auditable, safety-checked record of what happened.

Quick Start

Run kb-batch with your operation and IDs, adding --execute only when the dry-run output looks correct.

Frequently Asked Questions about kb-batch

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

FAQPage Schema
How do I safely batch update work items and specification lifecycles in a knowledge base?

Batch knowledge base updates require a mandatory dry-run preview to validate changes before execution. You can resolve work items, promote spec statuses, or retire superseded specs in controlled batches of up to 50 validated IDs to prevent unintended updates.

What is the maximum number of work item IDs allowed in a batch knowledge base update?

The maximum batch size for updating work item IDs is 50. The batch operation validates all provided IDs to ensure they exist and rejects oversized batches before proceeding with any knowledge base updates.

Do I need owner approval to batch resolve defect or regression work items?

Yes, batch resolving defect or regression work items requires owner approval confirmation through a GOV-15 governance gate. This ensures governed changes are explicitly authorized before any knowledge base modifications are applied.

How do I promote specification statuses from implemented to verified in bulk?

To promote specification statuses in bulk, submit the target spec IDs using the promote-specs operation. The system requires a dry-run preview first and automatically generates batch change reasons to maintain an auditable governance record.

What are the limitations of performing batch operations on knowledge base specifications?

Batch operations are limited to 50 validated IDs per run and require a mandatory dry-run before execution. Additionally, defect or regression origins require GOV-15 owner approval gating, which blocks execution without explicit confirmation.

How do I retire superseded knowledge base specifications safely?

To retire superseded knowledge base specifications safely, use the retire-specs operation with the target IDs. A mandatory dry-run preview shows exactly what will be retired before you apply the final changes using the execute flag.