prepare-release Eval-Bericht.

Validierungsplan

Was der Agent als Nächstes tun sollte

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Nicht verwenden, wenn

Bedingungen für eine andere Skill

• Teams, die ein vom Anbieter unterstütztes SLA benötigen
• production agents without a repository review
• The skill directly executes `pnpm build:builtin-knowledge` and creates git branches/PRs without explicit user confirmation beyond the initial request. This could lead to unintended side effects if the agent is misused or the user input is misinterpreted.
• Hinweise auf Hochrisiko-Berechtigungen: Shell- oder Befehlsausführung
• There is no explicit handling of prompt injection from commit messages or other repository content. While the skill only extracts `release-note` blocks, an attacker could craft commit messages to inject instructions into the release-note generation step (though the LLM is expected to follow the skill's rules).
• Production credentials, payments, or irreversible account changes without explicit human review