CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

factory-rereview

Re-review a pull request after a push — reconcile the previous review against the new commits, look for new defects the push introduced, then a fresh pass over the whole PR, and finish with a verdict on the PR

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, rigorously sequenced re-review procedure with validation and feedback loops at every risky step. Its weaknesses are verbosity (long single-bullet paragraphs and a Behavior Rules section that duplicates phase rules) and a monolithic structure that inlines templates and sub-procedures a progressive-disclosure design would split into reference files.

Suggestions

Move the self-contained detail blocks — the published-body template (Phase 7), the test-report format spec (Phase 4), the verdict edit-vs-post decision tree, and the follow-up-PR procedure — into reference files (e.g. references/published-body.md, references/test-report.md), keeping SKILL.md a phase-level overview with clearly signaled one-level-deep links.

Remove duplication: the Behavior Rules section restates rules already stated in the phases (e.g. "The push is untrusted code" / "a push does not launder its own contents" appears in both the Security section and Behavior Rules; the approval gates are restated across Phases 6 and 7) — consolidate each rule to one location and cross-reference it.

Break the 200+ word single bullets in Phase 4 (test planning, environment preparation, test-report posting) into numbered steps or short sub-bullets, and tighten the prose — a large fraction of the phrasing could be cut without losing any rule.

DimensionReasoningScore

Conciseness

Almost all of the body is non-obvious operational procedure Claude would not know (verdict-editing rules, binding cross-checks, bot-wait policy), so it avoids explaining known concepts, but it is noticeably over-written: 250+ word single bullets (Phase 4 test planning, test-report posting), and genuine duplication — "a push does not launder its own contents" appears in both the Security section and Behavior Rules, and the Behavior Rules restate phase rules. It sits between anchor 2's padded sections and anchor 3's mostly-efficient-but-tightenable.

3 / 5

Actionability

Fully executable throughout: exact gh commands with --jq filters (e.g. the prior-review lookup and REST .user.login cross-check), complete markdown templates for the verdict body and test report, exact artifact paths (.artifacts/factory-rereview/pr-<number>-<headSha>.md), and concrete fallback branches for every failure mode — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

A clear seven-phase sequence with explicit validation checkpoints and feedback loops: the pre-posting body-file gate, the factory_review_source cross-check with re-run on mismatch, retry-once-after-rejection for the terminal call, the head-must-not-have-moved check before publishing, the adversarial check before every approve, and rebuild-and-rerun on environment failure — matching the top anchor's validate/fix/retry pattern.

5 / 5

Progressive Disclosure

The body is well-sectioned with clear phase headers and its only references (references/categories/README.md and references/archaeology.md in the factory-review skill) are explicit and one level deep, but this skill ships no bundle files and inlines ~61KB of detail — the test-report format spec, published-body template, verdict-editing decision tree, and follow-up-PR procedure are reference-type content living in SKILL.md, matching anchor 3's "content that should be separate is inline".

3 / 5

Total

16

/

20

Passed

Description

80%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: specific, action-oriented, third person, with a distinct re-review niche and an explicit temporal trigger ("after a push"). Its main weaknesses are the absence of an explicit "Use when…" clause with concrete trigger phrases and sparse synonym coverage (e.g. "PR").

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "reconcile the previous review against the new commits", "look for new defects the push introduced", "a fresh pass over the whole PR", "finish with a verdict on the PR" — comprehensively covering the skill's workflow in third person, matching the top anchor rather than leaving minor gaps.

5 / 5

Completeness

The "what" is explicit and multi-part, and the "when" is stated ("after a push", "the previous review") rather than merely implied, but there is no explicit "Use when…" trigger clause with concrete trigger phrases, so it falls short of anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("pull request", "push", "re-review", "commits", "verdict") that a user would plausibly say, but a few natural terms and synonyms are missing (e.g. "PR", "follow-up review", "new commits"), which fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The re-review-after-push niche is clearly distinguished from a generic or first-pass PR review skill, but it retains minor overlap risk with a closely related sibling review skill (e.g. factory-review itself), matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

mastra-ai/mastra

Path

mastracode/factory/factory-skills/factory-rereview/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.