Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Review a FlyDSL release candidate against published releases for API stability violations, including export paths, signatures, result interfaces, semantics, and deprecation windows.
$ npx skills add ROCm/FlyDSL --skill release-api-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ROCm/FlyDSL release-api-check --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/ROCm/FlyDSL.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-api-check .claude/skills/release-api-check && 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 "release-api-check" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/release-api-check into .claude/skills/release-api-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-api-check", 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/ROCm/FlyDSL/tree/main/.claude/skills/release-api-checkType 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 ROCm/FlyDSL --skill release-api-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ROCm/FlyDSL release-api-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-api-check .agents/skills/release-api-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-api-check" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/release-api-check into .agents/skills/release-api-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-api-check", 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 ROCm/FlyDSL --skill release-api-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ROCm/FlyDSL release-api-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-api-check .cursor/skills/release-api-check && 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 "release-api-check" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/release-api-check into .cursor/skills/release-api-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-api-check", 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/ROCm/FlyDSL.git --path .claude/skills/release-api-check--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 ROCm/FlyDSL --skill release-api-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ROCm/FlyDSL release-api-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-api-check .gemini/skills/release-api-check && 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 "release-api-check" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/release-api-check into .gemini/skills/release-api-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-api-check", 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 ROCm/FlyDSL release-api-checkInstalls 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 ROCm/FlyDSL --skill release-api-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-api-check .github/skills/release-api-check && 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 "release-api-check" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/release-api-check into .github/skills/release-api-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-api-check", 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 ROCm/FlyDSL --skill release-api-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ROCm/FlyDSL release-api-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ROCm/FlyDSL.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-api-check .opencode/skills/release-api-check && 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 "release-api-check" agent skill from https://github.com/ROCm/FlyDSL/tree/main/.claude/skills/release-api-check into .opencode/skills/release-api-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-api-check", 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.
release-api-checkReview a FlyDSL release candidate against published releases for API stability violations, including export paths, signatures, result interfaces, semantics, and deprecation windows.
Release API Check is an agent skill from ROCm/FlyDSL. Review a FlyDSL release candidate against published releases for API stability violations, including export paths, signatures, result interfaces, semantics, and deprecation windows. Use for release compatibility reviews and breaking-change checks.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Git. The repository describes itself as: FlyDSL is the Python front‑end of the project: a Flexible Layout Python DSL for expressing tiling, partitioning, data movement, and kernel structure at a high level.
Read from SKILL.md and the folder at commit 1941889. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitpython3From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Release API Check loads about 2.2k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 1,087 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.
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); files beside SKILL.md are not scanned.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,087 words (~2,154 tokens).
“Work in the FlyDSL repository and use docs/api_stability.md as the policy source. Produce a compatibility report with source locations and validation evidence. A review does not itself authorize tagging, publishing packages, or changing release status.”
Just SKILL.md in .claude/skills/release-api-check of ROCm/FlyDSL.
Open the folder on GitHubat commit 1941889
Release API Check 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 |
|---|---|---|---|---|---|---|
| Release API Check this skillROCm/FlyDSL | 288 | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
ROCm/FlyDSL
Tune and analyse a FlyDSL kernel at the LLVM level: pick a compile hint, function attribute, or AMDGPU backend flag, then PROVE it reached codegen.
ROCm/FlyDSL
Detect per-kernel GPU resource regressions (VGPR, SGPR, register spills, scratch, static LDS) by diffing the final ISA before and after a change, using its isaresourcetable.py helper.
ROCm/FlyDSL
Review a FlyDSL PR, commit, branch, kernel, or consuming module for API-stability compliance.
ROCm/FlyDSL
Connect to a remote host via SSH and build a Docker image with rocprofv3, aiter, and FlyDSL.
ROCm/FlyDSL
Debug FlyDSL GPU kernels that produce NaN, inf, wrong results, or crash.
ROCm/FlyDSL
Guided step-by-step wizard for producing a new FlyDSL GPU kernel from a requirement: classify the kernel type, pick a skeleton, fill in compute, add control flow / sync / LDS, then test on GPU.
Works with
Categories
Review a FlyDSL release candidate against published releases for API stability violations, including export paths, signatures, result interfaces, semantics, and deprecation windows. Release API Check is an agent skill from ROCm/FlyDSL. Review a FlyDSL release candidate against published releases for API stability violations, including export paths, signatures, result interfaces, semantics, and deprecation windows.
Release API Check fits situations like: release compatibility reviews and breaking-change checks.
Run `npx skills add ROCm/FlyDSL --skill release-api-check -a claude-code`. Or copy the skill folder (.claude/skills/release-api-check in ROCm/FlyDSL) into .claude/skills/release-api-check in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ROCm/FlyDSL --skill release-api-check -a codex`. Or copy the skill folder (.claude/skills/release-api-check in ROCm/FlyDSL) into .agents/skills/release-api-check in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ROCm/FlyDSL --skill release-api-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-api-check, .gemini/skills/release-api-check, .github/skills/release-api-check and .opencode/skills/release-api-check in your project.
Going by SKILL.md and its folder, Release API Check needs the command-line tools its instructions call (git and python3). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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. Review the folder before installing.
Release API Check has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Release API Check: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ROCm (a GitHub organization) maintains it in ROCm/FlyDSL, which has 288 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.
Source: ROCm/FlyDSL on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.