ci-readiness-check Skill
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, po Published by microsoft in FluidFramework.
What is ci-readiness-check Skill?
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, po Published by microsoft in FluidFramework. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use ci-readiness-check Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FluidFramework
- Skill file: .claude/skills/ci-readiness-check/SKILL.md
What it does
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, po
Skill instructions
<required You MUST ask the user the Step 1 mode-choice question before doing anything else. Do not pick a mode for them. Do not default to a mode. Auto/autonomous mode does NOT authorize you to skip this question - being in auto mode is never a valid reason to bypass the prompt. There are exactly two narrow exceptions where you MAY skip the Step 1 mode-choice question. Both must be applied conservatively; if you are not certain an exception applies, you MUST ask. 1. No-op since the last check in this conversation. The most recent CI readiness check in the current conversation already ran, and every change since then is obviously/provably outside the scope of any check the skill performs. Examples that qualify: edits only to comments; edits only to files outside any workspace package (e.g. files under .claude/, repo-root README.md / CHANGELOG.md, top-level docs not in a docs/ package). Watch out: docs/api/ and similar are themselves workspace packages — markdown inside a workspace packa
Explore related resources
Frequently asked questions
What is ci-readiness-check?
ci-readiness-check is a open-source AI agent skill with Copy skill directory. Use when the user explicitly asks for a CI check or to push their branch — e.g.
Who is ci-readiness-check best for?
ci-readiness-check is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install ci-readiness-check?
Install or run ci-readiness-check using Copy skill directory. Check ci-readiness-check for the latest setup command.
Is ci-readiness-check actively maintained?
ci-readiness-check may need a closer maintenance check before production use.
Auto-fetched from GitHub.
