Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does…
Install Nexus Release
$ npx skills add ProfSynapse/nexus --skill nexus-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ProfSynapse/nexus nexus-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/nexus-release .claude/skills/nexus-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nexus-release" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-release into .claude/skills/nexus-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ProfSynapse/nexus --skill nexus-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ProfSynapse/nexus nexus-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.skills/nexus-release .agents/skills/nexus-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nexus-release" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-release into .agents/skills/nexus-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProfSynapse/nexus --skill nexus-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ProfSynapse/nexus nexus-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.skills/nexus-release .cursor/skills/nexus-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nexus-release" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-release into .cursor/skills/nexus-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ProfSynapse/nexus.git --path .skills/nexus-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ProfSynapse/nexus --skill nexus-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ProfSynapse/nexus nexus-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.skills/nexus-release .gemini/skills/nexus-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nexus-release" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-release into .gemini/skills/nexus-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ProfSynapse/nexus nexus-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ProfSynapse/nexus --skill nexus-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.skills/nexus-release .github/skills/nexus-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nexus-release" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-release into .github/skills/nexus-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProfSynapse/nexus --skill nexus-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ProfSynapse/nexus nexus-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.skills/nexus-release .opencode/skills/nexus-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nexus-release" agent skill from https://github.com/ProfSynapse/nexus/tree/main/.skills/nexus-release into .opencode/skills/nexus-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nexus-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nexus-release- GitHub stars
- 154
- Token cost
- ~944 tokens
- SKILL.md length
- 430 words
- Files
- 9 (incl. scripts, references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does…
- Works in 5 steps: Cutting a release → follow… → Bringing user-facing docs in line (a… → Before pushing any tag you MUST get a… → …
- Asked to release
- SKILL.md covers Workflow, Map, Siblings and Editing this skill
- Runs Python scripts from its folder; calls python3 and npm
What it does
Nexus Release is an agent skill from ProfSynapse/nexus. Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does not. Use when asked to release, publish, ship, cut a release, bump the version, or tag a version, and when a release workflow did not fire, failed its version guard, or produced the wrong assets.
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts and reference files (for example `protocols/cut-release.md`, `protocols/doc-review.md` and `protocols/recover.md`).
It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions. The licence is MIT.
When your agent uses it
- Asked to release
- Bump the version
- When a release workflow did not fire
- Failed its version guard
Example prompts
- “/nexus-release”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Cutting a release → follow protocols/cut-release.md end to end, in
- Bringing user-facing docs in line (a phase of the above; also runnable on
- Before pushing any tag you MUST get a clean exit from the readiness
- The workflow did not run, failed its guard, or shipped the wrong assets →
- After a release session → protocols/self-refine.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6cb7bce. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nexus Release loads about 944 tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 430 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from ProfSynapse/nexus at commit 6cb7bce, republished under its MIT licence (© ProfSynapse). 430 words, ~944 tokens.
Download SKILL.mdSave it as
.claude/skills/nexus-release/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- nexus-release
- description
- Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does not. Use when asked to release, publish, ship, cut a release, bump the version, or tag a version, and when a release workflow did not fire, failed its version guard, or produced the wrong assets.
Nexus Release
Context: a Nexus release is one artifact — a bare X.Y.Z git tag on main.
Everything downstream (installing, building, naming the release, uploading
main.js / manifest.json / styles.css, provenance attestation) is done by
<repo>/.github/workflows/release.yml from the tagged commit. You never build
the release; you make the tagged commit correct and then tag it.
Two consequences shape everything here. The tag is the point of no return — the workflow reads the tree as committed at that tag. And the workflow guards only three things, so everything else is on you.
Path convention: <repo>/… means relative to the Nexus repo root. Bare paths
(protocols/…, scripts/…) are inside this skill.
Workflow
Cutting a release → follow
protocols/cut-release.mdend to end, in order. Do not improvise the sequence: several steps only have any effect before the tag exists.Bringing user-facing docs in line (a phase of the above; also runnable on its own) →
protocols/doc-review.md.Before pushing any tag you MUST get a clean exit from the readiness check. It reproduces the workflow's own version guard locally, so a failure here is a failure you would otherwise discover after the tag exists:
bash python3 .claude/skills/nexus-release/scripts/check_release_ready.py --tag X.Y.Z(
--repodefaults to the repo root found by walking up from the working directory. Run--helpfor the flags; stdlib only, nonode_modules. If the mirror above is absent, the same file is at<repo>/.skills/nexus-release/scripts/check_release_ready.py.)The workflow did not run, failed its guard, or shipped the wrong assets →
protocols/recover.md. NEVER hand-create a release or hand-attach assets to fix it — that silently drops provenance attestation.After a release session →
protocols/self-refine.md.
Show full SKILL.md (171 more words)Show less
Map
protocols/the how:cut-release.md,doc-review.md,recover.md,self-refine.md.references/the why, read on demand:release-machinery.md(what the workflow really does, what it guards, what it does not, and the build-order asymmetry that decides which generated file can ship stale),changelog-format.md(the conventions the changelog actually follows).scripts/check_release_ready.py— version consistency acrosspackage.json,manifest.json,versions.json, the lockfile and the tag.refinement-log.md— what past releases taught this skill.
Siblings
Do not duplicate these; call them.
| Need | Skill |
|---|---|
| Regenerate the tool catalog a release must ship current | nexus-tool-schemas |
| Choose a Jest lane, or debug a failing guidance/drift test | nexus-testing |
| Provider/model metadata that a release happens to include | nexus-model-updates |
| Mobile or plugin-store compliance of what is being shipped | nexus-mobile-compat |
Editing this skill
<repo>/.skills/ is the source of truth for this skill; .claude/skills/,
.codex/skills/ and .cline/skills/ are mirrors written by
npm run sync:skills. Edit the copy under <repo>/.skills/nexus-release/ and
re-run the sync. The mirror copy overwrites changed files but does not delete
extra ones, so editing a mirror leaves a half-reverted hybrid on the next sync.
© ProfSynapse, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files (scripts, references) in .skills/nexus-release of ProfSynapse/nexus.
- SKILL.md
- protocols/cut-release.md
- protocols/doc-review.md
- protocols/recover.md
- protocols/self-refine.md
- references/changelog-format.md
- references/release-machinery.md
- refinement-log.md
- scripts/check_release_ready.py
Open the folder on GitHubat commit 6cb7bce
Compare with similar skills
Nexus Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nexus Release this skillProfSynapse/nexus | 154 | — | ~944 | Automated safety check: Pass | MIT | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Templatesbartstc/vite-ts-react-template | 122 | 13 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence |
Similar skills
- Official
GitHub Actions Templates
bartstc/vite-ts-react-template
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.
Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
CI Failure Triage and Repair
Chachamaru127/claude-code-harness
Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.
More from ProfSynapse/nexus
All 12 skills in this repoNexus Agents
ProfSynapse/nexus
How to add, change and verify a Nexus agent or tool, and the contract every tool must satisfy.
Nexus Eval Harness
ProfSynapse/nexus
Work on the Nexus LLM eval harness in tests/eval/ — author or fix a scenario fixture, write an eval config, change the executors, assertions or reports, or explain a run that produced nothing…
Nexus Model Eval
ProfSynapse/nexus
Grade how well a model drives the Nexus two-tool protocol (getTools/useTools) and decide whether a low score is the model's fault or the harness's.
Nexus Model Updates
ProfSynapse/nexus
Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint.
Nexus Storage
ProfSynapse/nexus
How to change, persist, migrate and recover Nexus data without losing it.
Nexus Testing
ProfSynapse/nexus
Verify a Nexus change — pick a Jest lane, write a test that can actually fail, run the in-app Obsidian CLI loop, drive the eval harness, or fix a shipped-docs drift failure.
Related
Works with
Categories
Questions about Nexus Release
What does Nexus Release do?
Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does…. Nexus Release is an agent skill from ProfSynapse/nexus. Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does not.
When should I use Nexus Release?
Nexus Release fits situations like: asked to release; bump the version; when a release workflow did not fire; failed its version guard.
How do I install Nexus Release in Claude Code?
Run `npx skills add ProfSynapse/nexus --skill nexus-release -a claude-code`. Or copy the skill folder (.skills/nexus-release in ProfSynapse/nexus) into .claude/skills/nexus-release in your project. Claude Code loads it when a task matches its description.
How do I install Nexus Release in Codex?
Run `npx skills add ProfSynapse/nexus --skill nexus-release -a codex`. Or copy the skill folder (.skills/nexus-release in ProfSynapse/nexus) into .agents/skills/nexus-release in your project. Codex loads it when a task matches its description.
Can I use Nexus Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ProfSynapse/nexus --skill nexus-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nexus-release, .gemini/skills/nexus-release, .github/skills/nexus-release and .opencode/skills/nexus-release in your project.
What does Nexus Release need to run?
Going by SKILL.md and its folder, Nexus Release needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and npm). Our summary lists: Python 3.
Does Nexus Release access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Nexus Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Nexus Release use?
Nexus Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nexus Release use?
About 944 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Nexus Release?
Skills that share tags, products or a category with Nexus Release: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nexus Release?
ProfSynapse (a GitHub user) maintains it in ProfSynapse/nexus, which has 154 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 2, 2026.
Source: ProfSynapse/nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.