theophile-wallez/LichessNeo / .claude/skills/ci
ci
VerifiedStart the release of main by hand (the CI, then a GitHub release of its zips), since no push runs it.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
SKILL.md
View on GitHub---
name: ci
description: Start the release of main by hand (the CI, then a GitHub release of its zips), since no push runs it.
disable-model-invocation: true
allowed-tools: Bash(git *), Bash(gh *), Bash(node scripts/version.ts *)
---
No push runs the CI, to spare the Actions minutes. This starts the Release
workflow on `main`: it runs the CI (checks, packages, end-to-end and Firefox
tests), then makes a GitHub release of main's zips. It doesn't reach the
stores: that's `/ci-publish`. Arguments: `$ARGUMENTS`; refuse any.
Pass `gh` the `origin` repository (`--repo <owner>/<repo>`, from `git remote
get-url origin`): the checkout has more than one remote.
1. It runs on what GitHub has, not the local checkout: `git fetch origin
--tags`, then compare `origin/main` with the local `main`. If local work
isn't on `origin/main` yet, say so and stop: don't push for the user.
2. `v=$(node scripts/version.ts --ref origin/main)`: the version it gets.
3. Start it: `gh workflow run release.yml --ref main`. Then find the run it
made (`gh run list --workflow release.yml --branch main --event
workflow_dispatch --limit 1 --json databaseId,url,status`; it may take a
few seconds to appear, so retry briefly) and give its URL and `v`.
Don't wait for the run to finish unless asked: its results are looked at
afterwards (`gh run view <id>`, `gh run watch <id>`).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |