running-ci-preflight

Catch the deterministic CI failures reachable from your diff before pushing, with `hogli ci:preflight`. Use when the pre-push hook blocks a push, before reporting a task done, or after editing Python, serializers, migrations, workflows, or dependency manifests — to avoid burning a CI matrix on a failure you could catch locally (formatting, lint, broken lockfiles, OpenAPI drift, migration conflict, stale branch). Trigger terms: ci:preflight, preflight, pre-push checks, pre-push hook failed, "will this break CI".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 focused, executable skill body with a clear re-run-until-clean loop, explicit validation, and well-organized sections. The only weakness is mild verbosity in a few Notes paragraphs that could be tightened without losing clarity.

Suggestions

Tighten the Notes bullets: the staleness and type-check paragraphs explain rationale at length that could be condensed to one line each while preserving the actionable flag/env names.

Consider moving the env-tunable staleness thresholds (HOGLI_PREFLIGHT_STALE_COMMITS/DAYS) into a short reference table so the prose stays scannable.

Dimension	Reasoning	Score
Conciseness	Mostly lean and Claude-aware, with concrete commands and no padding about what CI is, but several Notes paragraphs are dense and could be trimmed (e.g. the staleness and type-check rationale run long), keeping it just short of the fully-lean anchor.	4 / 5
Actionability	Provides the exact command `hogli ci:preflight --fix`, a literal status-symbol legend, and specific remediation commands (hogli build:openapi, git merge origin/master, env-tunable flags), giving copy-paste-ready guidance that covers the common cases.	5 / 5
Workflow Clarity	The numbered loop is a clear sequence with explicit validation checkpoints (read each line, resolve every fail, act on every advisory, re-run until clean then push) and a feedback loop for error recovery, matching the explicit-validation anchor.	5 / 5
Progressive Disclosure	A compact overview organized into well-signaled sections (The loop, Notes, Why it matters) with no bundle files and no nested references; for a sub-50-line skill with no external references this is appropriately structured and easy to navigate.	5 / 5
	Total	19 / 20 Passed

Description

100%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 tight, third-person description that covers what it does, when to use it, and natural trigger terms, with comprehensive concrete failure classes and no over-claims. It satisfies the what/when and trigger-term anchors fully.

Dimension	Reasoning	Score
Specificity	Names multiple concrete failure classes the check catches (formatting, lint, broken lockfiles, OpenAPI drift, migration conflict, stale branch) and the specific action (catch deterministic CI failures reachable from your diff before pushing), giving comprehensive coverage rather than minor gaps.	5 / 5
Completeness	Explicitly answers both 'what' (catch deterministic CI failures reachable from your diff before pushing) and 'when' (Use when the pre-push hook blocks a push, before reporting a task done, after editing Python/serializers/migrations/workflows/manifests) with concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit 'Trigger terms' line plus 'Use when' clauses list natural phrases a user would actually say (preflight, pre-push hook failed, 'will this break CI') including synonyms, matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The hogli ci:preflight niche is clearly distinct from its sibling ci:insights and scoped to pre-push deterministic failures, giving a clear niche with minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: PostHog/posthog
Path: .agents/skills/running-ci-preflight/SKILL.md
Commit: 06292db

Reviewed: 19 minutes ago

Table of Contents

Discovery Implementation Validation

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.