ci-readiness-check

Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.

Quality

88%

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

81%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 body is a well-sequenced, highly actionable CI-readiness workflow with strong validation checkpoints and feedback loops. Its main weakness is conciseness: the tree-package clean-build guidance is stated twice and the required exception block is lengthy.

Suggestions

Consolidate the @fluidframework/tree full-clean-build guidance into one place and defer detail to tree-api-checks.md instead of repeating it in Step 3 and the API-surface section.

Tighten the <required> exception block: the two skip-conditions can be stated more briefly without the extended examples and caveats.

Move the duplicated `pnpm clean && pnpm build` instructions behind the single tree-api-checks.md reference to reduce inline repetition.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and specific to the repo's CI process, but the @fluidframework/tree full-clean-build guidance is repeated in Step 3 and again in the "Determining if the public API surface changed" section, and the <required> exception block is verbose.	3 / 5
Actionability	Provides copy-paste-ready, executable commands throughout (e.g. `bash .claude/skills/ci-readiness-check/ci-readiness-check.sh [base-branch]`, `cd $PKG && pnpm exec fluid-build . -t eslint:fix`) covering the common cases.	5 / 5
Workflow Clarity	A clear 9-step sequence with explicit validation checkpoints (verify checks pass, git status, check reports afterward) and feedback loops (ae-missing-release-tag → add tag → rebuild → retry; unexpected diffs → full clean → regenerate).	5 / 5
Progressive Disclosure	Good section and step structure with one-level-deep, clearly-signaled references to tree-api-checks.md, though no bundle files exist; some content that could live in the referenced file is duplicated inline.	4 / 5
	Total	17 / 20 Passed

Description

95%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 is strong: it pairs an explicit Use-when clause with a rich set of natural trigger phrases and a concrete list of caught failure types. Its only minor gap is that it describes failure categories caught rather than a fuller set of actions performed.

Dimension	Reasoning	Score
Specificity	"Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations" lists several concrete failure categories, but the single action verb ("catches") keeps it just below fully comprehensive on actions performed.	4 / 5
Completeness	Explicitly answers both "what" (catches CI failures before pushing, with specifics) and "when" ("Use when the user explicitly asks for a CI check or to push their branch") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes comprehensive natural trigger phrases with synonyms — "ci readiness", "ci check", "pre-push check", "ready for CI", "ready to push", "push my changes", "push the branch", "let's push" — covering what users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear CI-readiness/pre-push niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: microsoft/FluidFramework
Path: .claude/skills/ci-readiness-check/SKILL.md
Commit: f02e424

Reviewed: 3 days 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.