check-ci
Skill4 starsChanged 4 months agoMITView on GitHub
Run the full CI pipeline locally, mirroring the checks in .github/workflows/ci.yml. Use to verify everything passes before pushing.
- Commits and pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- xmtp/libxmtptheir own version, first seen Oct 17, 2026
- kaeawc/auto-mobiletheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- xmtp/libxmtp★ 128same name
- kaeawc/auto-mobile★ 56same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- lintSkill
- propagate-templatesSkill
- test-hooksSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run the full CI pipeline locally, mirroring the checks in .github/workflows/ci.yml.
- Distinctive: line 23
Run each check in sequence.
- Very specific: line 67
Verify .claude-plugin/marketplace.json is valid JSON and all plugin source directories exist.
- Very specific: line 71
Verify every plugin in plugins/*/ and external_plugins/*/ has a valid .claude-plugin/plugin.json.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Check CI — Local CI Pipeline
Run the full CI pipeline locally, mirroring the checks in .github/workflows/ci.yml.
Command
/check-ciWorkflow
Run each check in sequence. Stop and report if any check fails.
1. Shell Formatting (lint-shell)
find . -name '*.sh' -not -path './node_modules/*' | xargs shfmt -i 2 -bn -sr -d2. Shell Lint (lint-shell)
find . -name '*.sh' -not -path './node_modules/*' | xargs shellcheck --shell=bash3. Markdown Lint (lint-markdown)
npx markdownlint-cli2 '**/*.md'4. Markdown Formatting (lint-markdown)
npx prettier --check '**/*.md'5. Template Drift — principled-docs (validate)
bash plugins/principled-docs/skills/scaffold/scripts/check-template-drift.sh
bash scripts/check-cross-plugin-drift.sh
bash scripts/check-skill-references.sh
bash scripts/pipeline-audit.sh
npx bats tests/10. Root Structure Validation (validate)
bash plugins/principled-docs/lib/validate-structure.sh --root11. Marketplace Manifest Validation (validate)
Verify .claude-plugin/marketplace.json is valid JSON and all plugin source directories exist.
12. Plugin Manifest Validation (validate)
Verify every plugin in plugins/*/ and external_plugins/*/ has a valid .claude-plugin/plugin.json.
13. Smoke-test ADR Immutability Hook (validate)
For each docs/decisions/*.md with status: accepted, feed its path to check-adr-immutability.sh and verify exit code 2 (block). Also test a non-decision file and verify exit code 0 (allow).
14. Smoke-test Proposal Lifecycle Hook (validate)
For each docs/proposals/*.md with terminal status, feed its path to check-proposal-lifecycle.sh and verify exit code 2. For draft proposals, verify exit code 0.
15. Smoke-test Manifest Integrity Hook (validate)
Feed .impl/manifest.json path to check-manifest-integrity.sh and verify exit code 0 (advisory). Feed an unrelated path and verify exit code 0 (silent passthrough).
16. Smoke-test PR Reference Hook (validate)
Feed gh pr create --title "test" --body "test" command to check-pr-references.sh and verify exit code 0 (advisory). Feed an unrelated command and verify exit code 0 (silent passthrough).
17. Smoke-test Review Checklist Hook (validate)
Feed gh pr review 42 and gh pr merge 42 commands to check-review-checklist.sh and verify exit code 0 (advisory). Feed an unrelated command and verify exit code 0 (silent passthrough).
18. Smoke-test Release Readiness Hook (validate)
Feed git tag v1.0.0 command to check-release-readiness.sh and verify exit code 0 (advisory). Feed git tag -l and verify exit code 0 (silent passthrough). Feed an unrelated command and verify exit code 0 (silent passthrough).
Summary
Report pass/fail for each step. If all pass, confirm the repo is CI-clean. If any fail, list the failures and suggest fixes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

