Relay10 review

Skill minwoo19930301/relay10/plugins/relay10/skills/relay10-review

Review a fixed change set for specification compliance, correctness, security, regression risk, and evidence quality. Use for code or release review; remain read-only unless the user separately requests fixes.From its SKILL.md

Install

npx -y skills add minwoo19930301/relay10 --skill relay10-review

Assembled 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.5 KB, 250 tokens by cl100k_base, as published. Nobody here has run it

DisciplinedRun Review

Review the requested baseline, not a moving or assumed diff.

Establish the baseline

Identify the exact commit, branch diff, patch, or working-tree changes in scope.
Read the specification and acceptance criteria.
Inspect relevant tests, runtime paths, configuration, and failure handling.

Two passes

First check specification compliance: missing behavior, scope drift, unsupported claims, and unmet acceptance criteria.

Then check code quality: correctness, security, data loss, concurrency, compatibility, dependency risk, observability, and test adequacy. Increase depth with risk; do not manufacture low-value comments to fill a quota.

Finding contract

Each actionable finding includes:

severity and concise title;
exact file and line or reproducible location;
evidence and failure scenario;
impact;
smallest safe remediation.

Separate findings from optional improvements. If no actionable findings exist, say so and name any residual testing gaps.

Boundaries

Do not edit during a review-only request.
Do not call tests passing if they were not executed.
Do not treat the maker's self-review as independent evidence.
Do not conflate clarity review with correctness or security review.