Audit qyl for compatibility drift, plane violations, generator/runtime mismatches, workflow-shape problems, policy gaps, and migration blockers by inspecting the repo directly.
From qylnpx claudepluginhub ancplua/ancplua-claude-plugins --plugin qylThis skill uses the workspace's default tool permissions.
references/compatibility.mdreferences/generator-runtime.mdreferences/migration.mdreferences/planes.mdreferences/policy-gates.mdreferences/repo-map.mdreferences/workflow-shape.mdAutomatically extracts reusable patterns like error resolutions, workarounds, and debugging techniques from Claude Code sessions via Stop hook, saving them as learned skills for reuse.
Observes Claude Code sessions via hooks to create atomic project-scoped instincts with confidence scores, evolving them into skills, commands, or agents.
Provides patterns for continuous autonomous agent loops with loop selection, quality gates, evals, recovery controls, and failure mitigation. Useful for production AI agent workflows.
qyl-audit is a strict repo audit skill.
It compares declared repo truth with observed repo state.
It is not a general architecture advisor. It is not a runtime subsystem. It is a read-only audit procedure.
Use this skill when the user asks to:
Always start with the minimum repo truth surface:
AGENTS.mdCLAUDE.md.claude/AGENTS.md.claude/planes/*.mdCHANGELOG.mdVersion.propsThen read only the project and source files needed for the requested audit mode.
Use the reference files in references/ for audit rules and compatibility facts.
If no mode is given, run all of these:
compatCheck package/API truth against actual usage.
Read:
Version.props*.csprojUse:
references/compatibility.mdplanesCheck seven-plane boundary violations and instruction-surface consistency.
Read:
.claude/AGENTS.md.claude/planes/*.mdAGENTS.mdCLAUDE.mdUse:
references/planes.mdreferences/repo-map.mdgeneratorCheck Loom model -> emitted output -> runtime bridge parity.
Read:
src/qyl.instrumentation.generators/Loom/**src/qyl.instrumentation/Instrumentation/Loom/**.g.cs outputs if presentUse:
references/generator-runtime.mdworkflowCheck whether orchestration follows the intended MAF shape.
Read:
src/qyl.loom/**src/qyl.collector/Autofix/**Use:
references/workflow-shape.mdpolicyCheck capability and approval coverage.
Read:
Use:
references/policy-gates.mdmigrationCheck whether old paths can be removed.
Read:
CHANGELOG.mdUse:
references/migration.mdTreat compatibility facts as embedded audit knowledge, verified against repo versions.
Examples of valid built-in facts:
.NET 10 AIFunctionFactoryOptions is the preferred Loom tool bridge pathConfigureParameterBinding, MarshalResult, and ExcludeResultSchema are the important .NET 10 bridge featuresDo not invent new compatibility facts from memory if the repo version surface can be checked directly.
Migration state is not hardcoded.
Derive it live from:
CHANGELOG.mdReturn a plain markdown report.
Do not invent JSON schemas or custom data envelopes unless the user explicitly asks for them.
Use this section order when relevant:
List findings first, ordered by severity.
Each finding should include:
List the exact files that support the findings.
List the missing conditions that prevent cleanup, migration, or deletion.
Only list items here if:
If any of those are false, do not list it as safe.
Include:
Use when:
Use when:
Use when:
Prioritize these qyl surfaces when relevant:
src/qyl.collectorsrc/qyl.contractssrc/qyl.instrumentationsrc/qyl.instrumentation.generatorssrc/qyl.loomsrc/qyl.mcp.claude/planesCHANGELOG.mdVersion.propsLoad only what is needed:
references/compatibility.mdreferences/planes.mdreferences/generator-runtime.mdreferences/workflow-shape.mdreferences/policy-gates.mdreferences/migration.mdreferences/repo-map.md