bulk-campaign

Executes batched, progress-tracked multi-file documentation changes across a scoped MariaDB docs path.

28|115|Updated Jan 28, 2025
One-click install
npx skills add https://github.com/mariadb-corporation/mariadb-docs --skill bulk-campaign-mariadb-corporation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bulk-campaign
Source: https://github.com/mariadb-corporation/mariadb-docs/tree/main/.claude/skills/bulk-campaign
Command: npx skills add https://github.com/mariadb-corporation/mariadb-docs --skill bulk-campaign-mariadb-corporation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Applying the same change across hundreds of documentation files by hand is error-prone, hard to review, and easy to abandon mid-way. This Skill turns a repo-wide documentation pass into a controlled campaign: a confirmed work-list, small reviewable batches, per-file verification, and a resumable progress log tied to a DOCS ticket. ## Core Features & Use Cases - Scoped work-list discovery: Enumerates matching .md files within one space/path, reports counts and exclusions, and requires confirmation before editing. - Batched processing with verification: Applies the transformation in batches of ~5 files, re-reads each change, runs doc-lint validation, and commits per batch only with explicit approval. - Resumable progress tracking: Maintains a gitignored state file recording done/failed files so long campaigns can stop and resume without rework. - Use Case: For a ticket like DOCS-5614 ("add railroad diagrams to N more SQL pages"), the Skill builds the list of SQL-statement pages, processes them in small commits, logs factual claims to the campaign report, and produces a final done/failed summary. ## Quick Start Ask the AI to run a bulk campaign that adds railroad diagrams to all SQL-statement pages under server/reference/sql-statements/ tracked under your DOCS ticket.

Frequently Asked Questions about bulk-campaign

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

FAQPage Schema
How do I apply the same edit to many Markdown documentation files?▼

Define the transformation, a single space/path scope, and a DOCS tracking ticket. The Skill enumerates matching .md files, confirms the work-list with you, then processes files in batches of about five with per-file verification and per-batch commits.

How to rename a term across an entire documentation space safely?▼

Scope the rename to one space and path, never the whole repo. The Skill builds the file list, applies the rename in small reviewable batches, validates each file with doc-lint, and records failures rather than skipping files silently.

Can a long documentation campaign be resumed after stopping?▼

Yes. Progress is persisted to a gitignored state file .claude/bulk-campaign.local.json recording done and failed files. On resume, the Skill reads the state, skips completed files, and continues from where it stopped.

Does the bulk campaign push commits or open pull requests?▼

No. The Skill commits one batch at a time only with explicit approval, using the DOCS ticket key in the message. It never runs git push and never opens a PR; the user handles pushing and PR creation.

What are the limitations of a bulk documentation campaign?▼

It operates on one space/path at a time and requires an explicit confirmed scope. Large structural passes like mass moves or SUMMARY.md reordering can collide with GitBook sync, so content-only edits in place are preferred.