meta-apply

Applies staged skill-corpus patches after fresh cross-model jury review and human approval.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill meta-apply-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-apply
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/meta-apply
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill meta-apply-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Self-modifying AI skill systems need a hard boundary between proposing changes and landing them; without it, a loop could apply its own patches or trust forgeable verdicts. This Skill is the only privileged gate that mutates the skill corpus, enforcing human authorization plus a fresh cross-model jury verdict on every staged patch. ## Core Features & Use Cases - Jury-at-landing verification: Runs a fresh cross-model codex jury on each staged diff at landing time, ignoring any producer-written verdict that could be forged. - Privileged corpus mutation: Applies approved patches via Write/Edit with automatic backups to .aris/meta/backups/ and provenance stamping (author, reviewer, verdict ID, content hash). - Audit logging and tracing: Records every landing to .aris/meta/optimizations.jsonl and saves jury traces for forensic recovery. - Use Case: After running /meta-optimize and reading its report, you type /meta-apply 1,3 to land only the patches you named, each re-judged by a fresh codex jury before any file changes. ## Quick Start After reviewing the staged patches from a /meta-optimize run, ask the assistant to run /meta-apply with the patch numbers you want to land.

Frequently Asked Questions about meta-apply

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

FAQPage Schema
How do I apply staged patches from meta-optimize?

Run /meta-apply with the patch numbers you want to land, such as /meta-apply 1,3 or all. Each named patch is re-judged by a fresh cross-model codex jury at landing time, and only jury-PASSED patches are applied to the corpus.

Why does meta-apply re-run the jury instead of trusting the producer verdict?

A producer-written jury_verdict field is forgeable, since the same process that staged the patch wrote it. Meta-apply runs its own fresh codex jury on the actual staged diff at landing time, so the verdict is produced where it is consumed.

Can a human override a jury KILL verdict?

No. The human can only choose which jury-PASSED patches to land; a KILL verdict cannot be overridden. This keeps the reject-default rule structural rather than advisory.

What happens if a landed patch causes problems later?

Every mutation is backed up to .aris/meta/backups/<date>/ before applying, so any landed patch is revertable from its backup. The provenance stamp includes a content hash, so later hand-edits invalidate the stamp.

Does meta-apply run automatically after meta-optimize?

No. It is human-invoked only and never runs as a side effect of another skill or hook. The explicit user invocation is the landing authorization.