meta-apply

Apply verified self-modification patches to a software corpus after cross-model jury approval.

1|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/dogekiki/SP-test --skill meta-apply-dogekiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-apply
Source: https://github.com/dogekiki/SP-test/tree/main/.trae/skills/meta-apply
Command: npx skills add https://github.com/dogekiki/SP-test --skill meta-apply-dogekiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the risk of uncontrolled self-modification by acting as a secure, human-authorized gatekeeper that validates and applies patches generated by autonomous optimization agents.

Core Features & Use Cases

  • Jury-at-Landing: Performs an independent, cross-model verification of every patch before it is applied to the codebase.
  • Provenance Tracking: Automatically stamps every applied change with author, reviewer, and verdict metadata for full auditability.
  • Use Case: After an optimization agent proposes a series of performance improvements, use this skill to review the jury's verdict and selectively land only the safe, approved patches into your production code.

Quick Start

Type /meta-apply all to review and land all pending patches that have passed the cross-model jury verification.

Frequently Asked Questions about meta-apply

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

FAQPage Schema
How do I securely apply self-modification patches to a codebase?

To securely apply self-modification patches, you need a gatekeeper that enforces privilege boundaries, mandates cross-model jury verification, and requires human authorization before transitioning staged candidates to permanent code changes.

What is cross-model jury verification for code review?

Cross-model jury verification is an independent review mechanism that validates every patch before application, ensuring autonomous optimization agents cannot land uncontrolled or unauthorized mutations directly into production code.

How do I track provenance for applied code patches?

You track provenance by automatically stamping every applied change with author, reviewer, and verdict metadata, ensuring full auditability and structural integrity for all self-modification patches.

Can I selectively land approved patches from an optimization agent?

Yes, you can review the jury's verdict and selectively land only the safe, approved patches into your production code, preventing unauthorized direct mutations to the software corpus.

Does automated patch management prevent unauthorized direct mutations?

Automated patch management prevents unauthorized direct mutations by enforcing a secure privilege boundary that requires mandatory cross-model jury verification and human authorization before any permanent code changes occur.