meta-apply

Apply user-selected patches to the skill corpus after a fresh cross-model jury verdict.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/xqinag/ARIS-new --skill meta-apply
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-apply
Source: https://github.com/xqinag/ARIS-new/tree/main/skills/meta-apply
Command: npx skills add https://github.com/xqinag/ARIS-new --skill meta-apply

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Privileged applier ensures only user-approved patches can modify the skill corpus, preventing uncontrolled self-modification.

Core Features & Use Cases

  • Jury-at-landing: executes a fresh cross-model jury on the staged .diff and target before landing.
  • Human-in-the-loop landing: requires explicit user invocation to approve and land patches.
  • Backups and provenance stamping: backs up targets and stamps provenance for auditability.
  • Strict separation of roles: enforces author ≠ reviewer family and guards against forged verdicts.

Quick Start

Invoke /meta-apply with the patch numbers you want to land to authorize the landing.

Frequently Asked Questions about meta-apply

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

FAQPage Schema
How do I safely apply self-modification patches to a skill corpus?

Landing self-modification patches safely requires a controlled process that enforces human approval, creates backups, and stamps provenance to guarantee auditable, reversible mutations. This prevents uncontrolled changes to your skill corpus.

What is a cross-model jury verdict for patch governance?

A cross-model jury verdict is a governance mechanism where multiple AI models from different families evaluate a staged diff before patch landing. It enforces strict separation of author and reviewer families to guard against forged verdicts.

How do I land staged diffs with human-in-the-loop approval?

You land staged diffs by explicitly invoking the patch application command with your selected patch numbers. The system requires explicit user invocation to authorize and land only the user-selected patches you approve.

Can I reverse a patch landing if the mutation breaks my corpus?

Yes, patch landing is reversible because the system backs up target files before applying mutations. Combined with provenance stamping on landing events, you can audit and rollback unwanted changes to the corpus.

Does patch governance enforce provenance checks across different model families?

Yes, patch governance enforces cross-family provenance checks to ensure the author and reviewer come from different model families. This strict separation of roles prevents conflicts of interest and guards against forged verdicts.