# Evozeus Wrapper Evolution Loop

> Use for lesson intake and Issue-to-PR flow after a Skill has an EvoZeus-CoEvolve harness.

- Skill: `metainflow/evozeus-wrapper-evolution-loop` (Agent Skill)
- Install (CLI): `npx get-skill add metainflow/evozeus-wrapper-evolution-loop`
- Raw SKILL.md: https://api.skillmd.com/api/skills/metainflow/evozeus-wrapper-evolution-loop/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: metainflow (https://skillmd.com/u/metainflow)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/metainflow/evozeus-wrapper-evolution-loop

---


# Evolution Loop

Use this stage after the target Skill is wrapped and installed through canonical repo pointers.

## Lesson Intake

```bash
python3 scripts/evozeus_wrapper.py loop lesson --dry-run --json
```

Ask the user whether to submit a lesson candidate. If approved, submit it as an Issue or lesson entry after checking sensitive data.

## Feedback Audit

```bash
python3 scripts/evozeus_wrapper.py loop audit --target /absolute/path/to/skill --user-input "<input>" --json
```

Use this when the user corrected the agent, expressed dissatisfaction, identified a reusable Skill/wrapper defect, or asked to preserve a repeatable behavior. The command returns whether to capture feedback, a short signal id, a structured `user_notice`, route, severity, evidence boundary, and an Issue draft. It does not persist a signal or write GitHub.

When `should_capture=true`, finish the current business correction first, then show `user_notice.display_text` as a separate block at the end of the same response. The action must ask whether to record the Lesson and state that recording does not start a fix. The signal exists only in the current invocation, no Issue was created, no Skill was modified, and no PR was opened.

The marker contract is:

```text
💡 `EvoZeus · Lesson` 待记录

<reusable lesson summary>

是否记录到 Skill Feedback Issue？本次授权仅用于记录，不启动修复。
```

Authorization is staged:

1. Feedback capture creates `LOCAL_PENDING_CONFIRMATION` only.
2. Create an Issue only after explicit user confirmation.
3. Issue approval does not authorize a fix, branch, design doc, or PR.
4. Enter Issue-to-PR only after a separate explicit request to implement the fix.

## Issue-to-PR

```bash
python3 scripts/evozeus_wrapper.py loop issue-to-pr --dry-run --json
```

Run this stage only after the feedback Issue exists and the user separately authorized implementation.

Before creating a PR, check GitHub permissions:

- write access: branch and PR in canonical repo.
- fork access only: fork and PR.
- no PR permission: local patch/design doc only.

## Stop Conditions

- Lesson contains raw private session, secret, customer data, or unredacted commercial context.
- `gh auth` fails.
- Private repo access is missing.

