deploy
Skill1.5k starsChanged 4 days agoMITView on GitHub
Prepare and ship a **gemma-macos-tuner** release (PyPI) or verify release readiness. Before any publish, run the same blocking gates as CI (Ruff, fast tests, pre-commit when applicable); fix failures before tagging. Use when the user asks to publish to PyPI, cut a release, verify a version tag against pyproject.toml, or confirm release automation. Do not use for ad-hoc training runs or local-only work unless release hygiene is explicitly the goal.
- Installs packages
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 137 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Do not tag or advise a release until every applicable step succeeds (exit 0):
- Distinctive: line 28
On failure: stop, fix root cause, re-run from step 2.
- Very specific: line 32
Read README.md and .github/workflows/publish-pypi.yml for tag ↔ version rules and secrets.
- Distinctive: line 33
Run Pre-publish gate (blocking).
- Very specific: line 36
After a successful publish (or dry-run build), note the artifact paths under dist/ if relevant.
“Common” is measured: kept by at least 6 in 10 of the 137 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
Deploy / release (gemma-tuner-multimodal)
This skill targets this repository: Python package gemma-macos-tuner (pyproject.toml), macOS-first CI (.github/workflows/ci.yml), and PyPI publish on version tags (.github/workflows/publish-pypi.yml). There is no Cloudflare Worker or wrangler surface in this repo.
What gets shipped
| Surface | How it ships |
| PyPI package | Tag v<version> where <version> matches project.version in pyproject.toml; workflow builds sdist/wheel and runs twine upload (needs PYPI_TOKEN in repo secrets). |
Canonical version truth: pyproject.toml project.version.
Pre-publish gate (blocking)
Do not tag or advise a release until every applicable step succeeds (exit 0):
- Install dev deps:
pip install -e '.[dev]'(and CPUtorchfor tests if needed, matching CI—see.github/workflows/ci.yml). ruff check .ruff format --check .pre-commit run --all-files(when verifying full CI parity locally; optional if Ruff alone was requested).- Fast tests:
pytest -q -m "not slow"(or the subset CI runs—see workflow for explicit test list).
On failure: stop, fix root cause, re-run from step 2.
Procedure (agent)
- Read
README.mdand.github/workflows/publish-pypi.ymlfor tag ↔ version rules and secrets. - Run Pre-publish gate (blocking); do not continue until green.
- Tag discipline:
publish-pypirequiresv$VERSIONwhere$VERSIONequalsproject.versioninpyproject.toml(e.g. tagv1.1.0for version1.1.0). - Credentials:
PYPI_TOKENmust be configured on GitHub; do not commit tokens. User may runpython -m buildandtwine check dist/*locally without uploading. - After a successful publish (or dry-run build), note the artifact paths under
dist/if relevant.
CI parity
.github/workflows/ci.yml runs Ruff, pre-commit, and fast pytest on macOS arm64. Manual release prep should honor the same checks.
Anti-patterns
- Tagging when Ruff or tests are red.
- Bumping
pyproject.tomlversion without updating the tag format expected by CI. - Lowering coverage or lint thresholds to “make release green.”
Related docs
README.mddocs/CONTRIBUTING.mdREADME/notes/debug-notes.md
Other versions153 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 153
- ok-oldking/ok-wuthering-waves★ 8.4ksame name
- memovai/mimiclaw★ 5.8ksame name
- microsoft/agent-skills★ 3.2ksame name
- microsoft/skills★ 3.2ksame name
- jhd3197/ServerKit★ 1.8ksame name
- microsoft/azure-skills★ 1.6ksame name
- pedrohcgs/claude-code-my-workflow★ 1.6ksame name
- microsoft/power-platform-skills★ 1.1ksame name
- jazzyalex/agent-sessions★ 930same name
- awslabs/agent-plugins★ 918same name
143 more not listed
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.
Used alongsideProjects with it also use pm-discovery, qa-phase and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
- ww-w-aiSkill
qa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +10 more from ww-w-ai
In this repository20 other files it gives its agents.
- audit-fix-hardcoreSkill
- audit-fix-loopSkill
- auditSkill
- build-vs-buySkill
- create-planSkill
- create-skillSkill
- debugSkill
- documentationSkill
- elon-muskSkill
- execute-plan-hardcoreSkill
- execute-planSkill
- git-commitSkill
- git-pushSkill
- guide-ingestSkill
- ilya-sutskeverSkill
- markdownSkill
- phase-auditSkill
- research-debuggingSkill
- research-planningSkill
- write-notesSkill
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.