Patch generator
Auditable AgentTeams multi-agent software delivery with contract-driven Skills.
npx -y skills add YZYY95K/test --skill patch-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 12 days oldThe repository was created 12 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate a minimal structured candidate patch from verified located context. Use when TeamLeader delegates implementation after root-cause evidence exists, or when exact test or review evidence requires a bounded revision.
SKILL.md
1.6 KB, as published. Nobody here has run it
Patch Generator
Return a candidate Patch; Tester and Reviewer own promotion.
Procedure
- Validate
LocatedContext, repository revision, tier, and optional failure evidence. - Change only evidence-backed files and preserve public behavior outside the issue acceptance criteria.
- Add focused tests when behavior changes. Do not delete or weaken existing tests to obtain a pass.
- Produce repository-relative file changes and unified diffs.
- Check schema, path confinement, diff consistency, syntax, secret patterns, and dangerous execution patterns.
- Run
python scripts/validate.py output <artifact.json>and emitcoder.patch_ready.
Decision rules
- Regenerate invalid candidates at most three times using exact diagnostics.
- A revision may address supplied test/review findings only; unrelated cleanup is a new task.
- Escalate after the retry budget; never relax a gate.
Boundaries
Do not apply, push, test, approve, merge, or access credentials. Reject
absolute paths, traversal, default-branch writes, secret-shaped content,
eval, exec, os.system, and shell-enabled subprocesses.
Read the contract for the complete artifact and handoff rules. Read examples before handling multi-file or rejected candidates.