CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lightrun-runtime-aware-pr-review

Use when reviewing a pull request with runtime or production evidence — for example to review a PR with runtime verification, gather production evidence, or simulate a patch on live samples. Reviews a pull request by diffing against the PR merge base, checking Runtime History before collecting live samples for remaining gaps, and simulating the patch on captured production inputs.

Quality

89%

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

85%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.

A well-structured orchestration skill: clear phase sequencing with explicit validation checkpoints and feedback loops, and exemplary progressive disclosure with an annotated, verified one-level-deep reference bundle. Minor gains are available from trimming checkpoint duplication and adding one inline example of a phase artifact.

DimensionReasoningScore

Conciseness

The body is lean and operational with no explanations of known concepts, but the Checkpoints section one-line summaries partly duplicate the per-phase exit criteria held in the reference files, and a few Working Rules restate constraint content ('Follow every constraint in Constraints').

4 / 5

Actionability

Concrete, executable direction is given throughout — ordered phase references with per-phase artifacts, specific identifiers (pr_base_sha, deployed_sha), and concrete status vocabularies (covered, base-covered, head-covered, uncovered) — but the executable specifics (commands, tool schemas, message templates) all live in references with no inline example of a common case.

4 / 5

Workflow Clarity

The multi-phase process is explicitly sequenced ('Read and follow these references in order') with per-phase exit criteria checkpoints, explicit stop conditions (Phase 1 not-verifiable, Phase 5 Sampling Request), and a feedback loop ('loop back to the prior phase when evidence is incomplete').

5 / 5

Progressive Disclosure

The body is a clear overview that lists all 12 reference files in a numbered, annotated navigation list; every referenced path exists in the bundle, references are one level deep (cross-links are lateral siblings also linked directly from SKILL.md), and detail is appropriately deferred to the phase files.

5 / 5

Total

18

/

20

Passed

Description

88%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 with explicit what-and-when structure and multiple concrete capabilities. Trigger phrasing is natural but leans on product-specific terminology, and the broad opening phrase leaves slight conflict risk with general PR-review skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'diffing against the PR merge base', 'checking Runtime History', 'collecting live samples for remaining gaps', 'simulating the patch on captured production inputs' — which together comprehensively cover the skill's review pipeline.

5 / 5

Completeness

It explicitly answers both questions: an explicit 'Use when reviewing a pull request with runtime or production evidence' trigger clause with examples, and a clear statement of what it does (merge-base diffing, Runtime History check, live sampling, patch simulation).

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('reviewing a pull request', 'runtime verification', 'production evidence', 'simulate a patch on live samples'), but product-specific jargon ('Runtime History', 'merge base') dominates and common synonyms (e.g., 'production data', 'test on live traffic') are absent.

4 / 5

Distinctiveness Conflict Risk

The 'runtime or production evidence' qualifier carves a clear niche distinct from plain code review, but the lead trigger phrase 'reviewing a pull request' creates minor overlap risk with generic PR-review skills before the qualifier is applied.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

lightrun-platform/lightrun-ai

Path

skills/lightrun-runtime-aware-pr-review/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.