skill-edit-validation

Validates test assertions after editing skill markdown content to prevent stale-assertion CI failures.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill skill-edit-validation-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-edit-validation
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/skill-edit-validation
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill skill-edit-validation-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Editing wording in SKILL.md or prompt files can silently break tests that assert on exact phrases, causing confusing CI failures discovered long after the change. This Skill runs a content-assertion sweep immediately after such edits so stale assertions are found and fixed in the same changeset. ## Core Features & Use Cases - Targeted grep sweep: Extracts old vs. new phrasing from the edit and searches test files (audit, security, spec-gate, skill-mirror, prompt, workflow suites) for assertions referencing the old wording. - Assertion context review: Reads surrounding lines of each match to check substring matches and absence checks (e.g., not.toContain) that the new wording might violate. - Semantic registry migration: Moves brittle string assertions behind a named-concept registry (tests/helpers/skill-content-registry.ts) so tests assert behavioral intent rather than exact text. - Use Case: After rewording a spec-gate message from "spec.md does NOT exist" to "NO effective spec exists", sweep the test suite, update the two stale assertions, and migrate one to the semantic registry before committing. ## Quick Start After editing any skill markdown file, ask the agent to run the skill-edit-validation sweep to find and update any test assertions that reference the old wording.

Frequently Asked Questions about skill-edit-validation

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

FAQPage Schema
How do I find tests that break after editing skill prompt wording?

Extract the old and new phrasing from your edit, then grep test files for the old phrase using ripgrep (e.g., rg "old-phrase" tests/ src/ --type ts -l). Focus on audit, security, spec-gate, skill-mirror, prompt, and workflow test suites.

How do I update stale test assertions after changing markdown content?

Read the surrounding lines of each matching assertion to confirm whether it checks a substring or an absence condition, then update it to match the new wording in the same changeset. Preserve the behavioral intent of the test, not just the literal string.

When should tests use a semantic content registry instead of string matching?

Use a semantic registry when an assertion checks skill behavior rather than an exact contract string. Move the check behind a named concept in tests/helpers/skill-content-registry.ts so future wording changes do not break the test.

Why do CI tests fail after editing SKILL.md files?

Tests often assert on exact phrases or on the absence of specific words in skill content. Changing wording can break substring matches or introduce words that not.toContain checks forbid, causing stale-assertion failures.

What are the limitations of exact string assertions in skill tests?

Exact string assertions are brittle: any rewording breaks them even when behavior is unchanged. They should be reserved for exact contract strings, while behavioral checks should use named semantic concepts that survive wording edits.