ci-check
Skill83 starsChanged 39 days agoApache-2.0View on GitHub
Run the same checks as the ADK's GitHub CI (PR title, lint, format, licences, licenses.json, skill versions, tests) locally and report pass/fail. Use before pushing a branch or opening a pull request in the polyai-adk repo.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- Srltas/claude-skillstheir own version, first seen Oct 31, 2026
- J3vb/OwnCordtheir own version, first seen Oct 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- J3vb/OwnCord★ 11same name
- AxlZero21/Skills★ 1same name
- Srltas/claude-skills★ 0same 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-resource-typeSkill
- open-prSkill
- review-prSkill
- write-testsSkill
- poly-adk-branchingSkill
- poly-adk-conversationsSkill
- poly-adk-rtcSkill
- poly-adk-testingSkill
- poly-adk-workflowSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Run every step, even after one fails, then report a summary.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Run the ADK CI checks locally
Run every step, even after one fails, then report a summary. All commands run from the repo root
through uv run; don't activate the venv.
- PR title. Take the intended PR title (ask if it isn't known) and check it matches
^(feat|fix|chore|docs|ci|build|perf|refactor|style|test)(\(.+\))?!?: .+. Check that the type is right too: anything a user can see isfeat:. See the release table inAGENTS.md. - Lint:
uv run ruff check . - Format:
uv run ruff format --check . - Licences:
uv run licensecheck --zero - licenses.json is current:
uv run pip-licenses && git diff --exit-code licenses.json. A diff here means it needs committing. - User skill versions:
uv run python scripts/validate_skills.py - Tests:
uv run pytest src/poly/tests/
CI also runs the tests on Windows. Point out new code that could break there: hard-coded /
path joins, open() without encoding="utf-8", shell-specific commands, or file permission
assumptions.
Report
- One line per step: pass or fail.
- For each failure, the relevant error output (trim long logs).
- A final verdict: ready to push, or what to fix first.
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.