skills.rest
pedapudi
pedapudiCOMMUNITY
Explore all skills by this author →
GitHub

zicato-mutation-audit

Audit mutable surfaces of registered zicato inner harnesses and verify mutation markers.

4|2|Updated May 14, 2026
Search Tags:#cli inspection#marker validation#zicato#mutation audit#inner harness#mutation surface#forbidden ids
One-click install
npx skills add https://github.com/pedapudi/zicato --skill zicato-mutation-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zicato-mutation-audit
Source: https://github.com/pedapudi/zicato/tree/main/skills/zicato-mutation-audit
Command: npx skills add https://github.com/pedapudi/zicato --skill zicato-mutation-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies which parts of a registered zicato inner harness are mutable before an evolution run, helping prevent unresolved markers, unintended edits, and incorrectly specified forbidden ids.

Core Features & Use Cases

  • Mutation Surface Auditing: Lists span, file, and code mutation points with ids, kinds, locations, previews, and mutable-line totals.
  • Targeted Inspection: Filters mutation points by id glob or marker kind and displays either previews or full current content.
  • Machine-Readable Review: Emits JSON metadata for automated validation, review tooling, and comparisons across registrations.
  • Forbidden-ID Verification: Helps confirm that ids intended to be off-limits are spelled correctly and actually exist in the registered surface.
  • Use Case: Before trusting an evolve run, inspect coordinator-related mutation points, verify every marker resolves without warnings, and confirm the proposer brief's forbidden ids match the audited ids exactly.

Quick Start

Run the zicato mutation audit against the registered workspace to review all mutable points and verify the intended mutation surface.

Frequently Asked Questions about zicato-mutation-audit

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

FAQPage Schema
How do I audit mutation markers in a zicato workspace before an evolution run?▼

You can filter mutation points by id glob or marker kind to inspect specific editable points. The audit displays either previews or full current content, helping you verify coordinator-related mutation points and resolve warnings.

Can I get machine-readable JSON output for mutation surface inventory checks?▼

Forbidden-id verification confirms that ids intended to be off-limits are spelled correctly and actually exist in the registered mutation surface. This prevents incorrectly specified forbidden ids from causing unintended edits during evolution.

What is a mutation surface and when do I need to audit it?▼

Auditing the mutation surface requires the zicato CLI, a registered workspace, and correctly annotated span, file, or code mutation markers. Without these prerequisites, the audit cannot verify the mutable points or resolve marker warnings.

How do I verify forbidden ids against the registered mutation surface?▼

To verify forbidden ids, run the mutation audit and compare the proposer brief's forbidden ids against the audited ids exactly. This confirms the off-limits ids are spelled correctly and actually exist in the registered surface.

Related Skills

Explore More Software Engineering Skills→
pedapudipedapudi
4

zicato-bootstrap

Initialize and validate a zicato workspace with Google ADK adapter registration and deterministic smoke tests.

Community
Intermediate
Wike-CHIWike-CHI
2

evolver

Analyze runtime logs and generate auditable evolution assets for AI agents.

Community
Advanced
pedapudipedapudi
4

zicato-write-brief

Author and refine zicato brief.md contracts defining epoch objectives and mutation priorities.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate