CtrlK
BlogDocsLog inGet started
Tessl Logo

review-hog-perspective-logic-correctness

The Logic & Correctness review perspective for ReviewHog. Verifies that changed code does what it is supposed to do — business logic, edge cases, data transformations, and query / data-access correctness. Reports correctness issues only; security and performance are separate perspectives.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./products/review_hog/skills/review-hog-perspective-logic-correctness/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-structured, lean, and actionable, with concrete investigation commands and clear scope boundaries that keep the reviewer in lane. Main improvement opportunities are tightening the redundant restatement across sections and adding an explicit finding-format/verification step.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the 'Key questions' and 'What a valid finding looks like' sections partly restate the 'Primary investigation areas', leaving minor redundancy that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready ripgrep commands (e.g., `rg "calculate|compute|aggregate" --type py -A 5`) plus concrete 'Where to focus' and 'What to leave to other perspectives' lists; mostly executable with minor gaps in finding-output format guidance.

4 / 5

Workflow Clarity

Lays out a clear review process with explicit scope boundaries and notes that overlap is resolved by a separate downstream deduplication step; the skill is not destructive/batch so the 3-cap does not apply, though an explicit finding-format/validation step is only implicit.

4 / 5

Progressive Disclosure

No bundle files exist, so the single self-contained SKILL.md is evaluated on its own organization; clear section headers (investigation areas, commands, focus, exclusions, valid findings) make it easy to navigate, with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

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

The description clearly conveys the skill's scope and distinguishes it from sibling perspectives, but it lacks an explicit 'Use when...' trigger clause and leans on internal-system framing rather than natural user keywords. Completeness and trigger-term quality are the main weaknesses.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when reviewing a PR for logic or correctness bugs, off-by-one errors, broken calculations, or query/data-access mistakes').

Broaden trigger-term coverage with synonyms and concrete phrasings users actually say ('bug', 'wrong result', 'calculation error', 'edge case', 'data mapping') rather than relying on the internal 'perspective' framing.

Convert scope-area language into a short list of discrete concrete actions to lift specificity from 4 toward 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete action areas ('business logic, edge cases, data transformations, and query / data-access correctness', 'Reports correctness issues only'); framed as scope areas rather than enumerated discrete actions, leaving minor coverage gaps that keep it below 5.

4 / 5

Completeness

Clearly states what it does ('Verifies that changed code does what it is supposed to do') but provides no explicit 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant terms ('business logic', 'edge cases', 'correctness', 'data transformations') but is framed as an internal ReviewHog perspective rather than natural user-facing triggers, and misses common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

Explicitly carves out a distinct niche ('Reports correctness issues only; security and performance are separate perspectives'), with only minor overlap risk against sibling ReviewHog review perspectives.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PostHog/posthog
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.