skills.rest
friedbotstudio
friedbotstudioOFFICIAL
Explore all skills by this author →
GitHub

audit-baseline

Detect drift between on-disk baseline implementations and their specifications.

5|Updated Apr 29, 2026
Search Tags:#drift detection#hooks#baseline#frontmatter#json validation#checksum#ci audit
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill audit-baseline
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-baseline
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/audit-baseline
Command: npx skills add https://github.com/friedbotstudio/baseline --skill audit-baseline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It catches documentation and implementation drift in the baseline skill set before that drift breaks installs, CI, or downstream automation.

Core Features & Use Cases

  • Verifies hook, agent, skill, and command counts against the canonical baseline.
  • Checks required wiring and metadata in settings.json, project.json, and .mcp.json.
  • Confirms helper scripts, vendored licenses, and cross-document claims stay aligned across the repository.
  • Use it when you need a repeatable pass or fail audit after edits, before release, or in continuous integration.

Quick Start

Use the audit-baseline skill to scan the repository and report any drift between the files on disk and the baseline specification.

Frequently Asked Questions about audit-baseline

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

FAQPage Schema
How do I detect baseline drift between my repository files and their specifications?▼

Baseline drift is detected by scanning the repository to compare files on disk against the baseline specification, verifying hook, agent, skill, and command counts. It applies read-only filesystem inspection and frontmatter parsing to catch implementation drift before release.

What is frontmatter parsing used for in CI audits?▼

Frontmatter parsing in CI audits validates project metadata and verifies required wiring in settings.json, project.json, and .mcp.json. It ensures cross-document claims and helper scripts stay aligned across the repository.

How do I validate JSON and metadata before a release verification?▼

JSON validation and metadata checks are performed during release verification by applying read-only filesystem inspection to settings.json and project.json. This confirms required wiring and metadata stay aligned with the canonical baseline.

Can I use checksum checks for maintenance reviews of vendored artifacts?▼

Checksum checks can be used during maintenance reviews to confirm vendored licenses and artifacts stay aligned across the repository. This optional validation runs alongside name and count comparisons to ensure baseline integrity.

Does this baseline drift detection require write access to the filesystem?▼

Baseline drift detection does not require write access because it uses read-only filesystem inspection. It safely audits hooks, commands, and project metadata without modifying the repository during continuous integration or maintenance reviews.

Related Skills

Explore More Software Engineering Skills→
cryborg1211cryborg1211

vc:watzup

Summarize repository state and active plans for handoff.

Community
Intermediate
BedaBeda-GrowthBedaBeda-Growth

app-baseline

Automate baseline verification and drift review with approval signatures.

Official
Advanced
motlinmotlin
14

precommit

Run precommit checks on code changes and report failures.

Community
Intermediate
jiten-singh-shahijiten-singh-shahi
13

sf-quickstart

Detect Salesforce project types and recommend SCC install profiles.

Community
Intermediate