Relay10 build
Skill minwoo19930301/relay10/plugins/relay10/skills/relay10-build
Implement an authorized repository change in small, verifiable slices. Use after scope and acceptance criteria are clear; do not use for diagnosis-only, review-only, or publication-only requests.From its SKILL.md
npx -y skills add minwoo19930301/relay10 --skill relay10-buildAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 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.
- 1 stars1 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.
SKILL.md
1.6 KB, 273 tokens by cl100k_base, as published. Nobody here has run it
DisciplinedRun Build
Apply the approved change while keeping evidence and rollback obvious.
Before editing
- Reconfirm the requested outcome, allowed mutations, and acceptance checks.
- Inspect the worktree and preserve unrelated user changes.
- Identify the smallest vertical slice that demonstrates progress.
- Add or update a failing test first when the behavior is testable and the test adds useful protection.
Do not force test-first mechanics for generated artifacts, trivial text edits, or behavior that is better verified by a deterministic validator. Record why when no test is appropriate.
Implementation loop
- Make one coherent change.
- Run the narrowest relevant check.
- Inspect the diff and unintended file changes.
- Continue only when the slice is understood.
- Run the broader regression set in proportion to risk.
Use structured argv and safe APIs rather than shell interpolation for untrusted values. Keep optional adapters and surfaces outside the core when possible.
Completion evidence
Report:
- files changed and why;
- tests or validators run with actual exit status;
- user-visible result;
- remaining risks or unsupported paths;
- rollback or revert point.
Do not claim completion from code inspection alone when executable verification is available. Do not commit, push, publish, tag, deploy, or send external messages unless the user authorized that action.