React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Semantic release and CI/CD lifecycle, conventional commit standards, release pipeline chain (release.yml and .releaserc), and git branching strategy.
Install Release Conventions
$ npx skills add kveld9/kveld-morphe-patches --skill release-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kveld9/kveld-morphe-patches release-conventions --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/kveld9/kveld-morphe-patches.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-conventions .claude/skills/release-conventions && 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-conventions" agent skill from https://github.com/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventions into .claude/skills/release-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-conventions", 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/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventionsType 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 kveld9/kveld-morphe-patches --skill release-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kveld9/kveld-morphe-patches release-conventions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kveld9/kveld-morphe-patches.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-conventions .agents/skills/release-conventions && 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-conventions" agent skill from https://github.com/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventions into .agents/skills/release-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-conventions", 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 kveld9/kveld-morphe-patches --skill release-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kveld9/kveld-morphe-patches release-conventions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kveld9/kveld-morphe-patches.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-conventions .cursor/skills/release-conventions && 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-conventions" agent skill from https://github.com/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventions into .cursor/skills/release-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-conventions", 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/kveld9/kveld-morphe-patches.git --path .agents/skills/release-conventions--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 kveld9/kveld-morphe-patches --skill release-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kveld9/kveld-morphe-patches release-conventions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kveld9/kveld-morphe-patches.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-conventions .gemini/skills/release-conventions && 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-conventions" agent skill from https://github.com/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventions into .gemini/skills/release-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-conventions", 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 kveld9/kveld-morphe-patches release-conventionsInstalls 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 kveld9/kveld-morphe-patches --skill release-conventions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kveld9/kveld-morphe-patches.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-conventions .github/skills/release-conventions && 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-conventions" agent skill from https://github.com/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventions into .github/skills/release-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-conventions", 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 kveld9/kveld-morphe-patches --skill release-conventions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kveld9/kveld-morphe-patches release-conventions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kveld9/kveld-morphe-patches.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-conventions .opencode/skills/release-conventions && 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-conventions" agent skill from https://github.com/kveld9/kveld-morphe-patches/tree/main/.agents/skills/release-conventions into .opencode/skills/release-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-conventions", 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
release-conventions- GitHub stars
- 113
- Token cost
- ~893 tokens
- SKILL.md length
- 345 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Semantic release and CI/CD lifecycle, conventional commit standards, release pipeline chain (release.yml and .releaserc), and git branching strategy.
- Works in 3 steps: Conventional Commits Standard → Release Pipeline Chain (release.yml &… → Branching Strategy
- Tasks that involve Commit messages
- SKILL.md covers 1. Conventional Commits Standard, 2. Release Pipeline Chain… and 3. Branching Strategy
- Calls python3 and jq
What it does
Release Conventions is an agent skill from kveld9/kveld-morphe-patches. Semantic release and CI/CD lifecycle, conventional commit standards, release pipeline chain (release.yml and .releaserc), and git branching strategy.
Its SKILL.md is about 890 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, covering Commit messages, Git workflow and CI/CD. It works with Git, Gradle and GitHub. The repository describes itself as: Custom Morphe patches on Android. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Commit messages
- Tasks that involve Git workflow
- Tasks that involve CI/CD
Example prompts
- “/release-conventions”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit bfc153e. 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
Shell commands in SKILL.md call:
python3jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Release Conventions loads about 893 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 345 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from kveld9/kveld-morphe-patches at commit bfc153e, republished under its GPL-3.0 licence (© kveld9). 345 words, ~893 tokens.
Download SKILL.mdSave it as
.claude/skills/release-conventions/SKILL.md (or your agent's skills folder).- name
- release-conventions
- description
- Semantic release and CI/CD lifecycle, conventional commit standards, release pipeline chain (release.yml and .releaserc), and git branching strategy.
Semantic Release & CI/CD Lifecycle
1. Conventional Commits Standard
Automated semantic releases depend on commit messages adhering strictly to the conventional commits specification configured in .releaserc:
| Prefix | Semver Impact | Release Notes Section | Trigger Automated Release? |
|---|---|---|---|
feat: | Minor (x.Y.0) | New Features | Yes |
fix: | Patch (x.x.Z) | Bug Fixes | Yes |
perf: | Patch (x.x.Z) | Improvements | Yes |
bump: | Patch (x.x.Z) | Updated App Support | Yes |
build(Needs bump): | Patch (x.x.Z) | Hidden | Yes |
refactor: | None | Code Refactoring | No (Documented in notes) |
chore: | None | Hidden | No (Skipped) |
docs: | None | Hidden | No (Skipped) |
Mandatory Atomic Commits Policy
Commit granularity (1 patch / 1 option / 1 fix = 1 commit, code and docs together) is defined in AGENTS.md, rule 14. Follow it exactly.
2. Release Pipeline Chain (release.yml & .releaserc)
When commits are pushed to main, the automated release pipeline executes:
- Commit Analysis: Evaluates commit log since previous release tag (
@semantic-release/commit-analyzer). - Release Notes Generation: Formats notes into sections based on conventional commit types (
@semantic-release/release-notes-generator). - Changelog & Bundle Generation:
@MorpheApp/changelogupdatesCHANGELOG.mdand generatespatches-bundle.json. - Gradle Version Bump:
gradle-semantic-release-pluginsyncsgradle.properties. - Catalog & Readme Generation: Executes prepare commands (
@semantic-release/exec):./gradlew generatePatchesList- Patches
patches-list.jsonwith next release version (jq '.version="${nextRelease.version}"' patches-list.json) - Generates updated README (
python3 .github/scripts/generate_patches_readme.py $GITHUB_REPOSITORY $GITHUB_REF_NAME patches-list.json README.md)
- Git Commit:
@semantic-release/gitcommits updated release assets (CHANGELOG.md,gradle.properties,patches-bundle.json,patches-list.json,README.md) with messagechore: Release v${nextRelease.version} [skip ci]. - GitHub Release & Asset Publishing: Attaches compiled standalone Morphe Patch Package (
patches/build/libs/patches-*.mpp) to the GitHub Release (@semantic-release/github). - Build Provenance Attestation: Attests build provenance for
patches/build/libs/patches-*.mppviaactions/attest-build-provenance. - Telegram Broadcast: Dispatches release tag, version, and notes via
python3 .github/scripts/notify_telegram.py. - Compilation Verification Fallback: When semantic-release does not publish a new release (e.g. for
refactor,chore,docs), CI executes./gradlew :patches:buildAndroid clean --no-daemonto ensure compilation integrity.
CRITICAL REMINDER: Never manually edit or commit
patches-list.json,patches-bundle.json, orCHANGELOG.md. These are generated, formatted, and committed strictly by CI during the automated release pipeline.
3. Branching Strategy
- Development and releases are anchored on
main; there is nodevbranch and no PR workflow (AGENTS.md, rule 15). - Automated releases trigger exclusively from
main. - Never force-push after a release tag has been created.
© kveld9, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/release-conventions of kveld9/kveld-morphe-patches.
Open the folder on GitHubat commit bfc153e
Compare with similar skills
Release Conventions 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 Conventions this skillkveld9/kveld-morphe-patches | 113 | — | ~893 | Automated safety check: Pass | GPL-3.0 | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 9.1k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Git Conventionswerf/werf | 4.7k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Git Changes ReporterNo-Trade-No-Life/Yuan | 352 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
Git Conventions
werf/werf
werf conventions for branch names and commit messages. An agent skill from werf/werf.
Git Changes Reporter
No-Trade-No-Life/Yuan
生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。
npm Package Publisher
klaudworks/universal-skills
Releases an npm package by committing changes, bumping the version with npm version, pushing the tag and checking the GitHub Actions publish.
More from kveld9/kveld-morphe-patches
Morphe Patcher
kveld9/kveld-morphe-patches
Architecture, patch typology (bytecodePatch, resourcePatch, rawResourcePatch), universal patches, stringOption DSL, fingerprint resolution, compatibility contracts (Constants.kt), and diagnostic…
Native Binary Patching
kveld9/kveld-morphe-patches
ARM64 ELF and binary asset patching guidelines covering libchrome.so host redirection, multi-candidate offset resolution, companion .so trimming, and Hermes bytecode patching.
Smali Bytecode Hooks
kveld9/kveld-morphe-patches
Smali and Dalvik bytecode hooking guidelines, register architecture conventions, multi-return reverse traversal, TwoRegisterInstruction extraction, reflection bridges, and obfuscation guidelines.
Related
Categories
Questions about Release Conventions
What does Release Conventions do?
Semantic release and CI/CD lifecycle, conventional commit standards, release pipeline chain (release.yml and .releaserc), and git branching strategy. Release Conventions is an agent skill from kveld9/kveld-morphe-patches.releaserc), and git branching strategy.
When should I use Release Conventions?
Release Conventions fits situations like: tasks that involve Commit messages; tasks that involve Git workflow; tasks that involve CI/CD.
How do I install Release Conventions in Claude Code?
Run `npx skills add kveld9/kveld-morphe-patches --skill release-conventions -a claude-code`. Or copy the skill folder (.agents/skills/release-conventions in kveld9/kveld-morphe-patches) into .claude/skills/release-conventions in your project. Claude Code loads it when a task matches its description.
How do I install Release Conventions in Codex?
Run `npx skills add kveld9/kveld-morphe-patches --skill release-conventions -a codex`. Or copy the skill folder (.agents/skills/release-conventions in kveld9/kveld-morphe-patches) into .agents/skills/release-conventions in your project. Codex loads it when a task matches its description.
Can I use Release Conventions 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 kveld9/kveld-morphe-patches --skill release-conventions -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-conventions, .gemini/skills/release-conventions, .github/skills/release-conventions and .opencode/skills/release-conventions in your project.
What does Release Conventions need to run?
Going by SKILL.md and its folder, Release Conventions needs the command-line tools its instructions call (python3 and jq). Our summary lists: Python 3.
Does Release Conventions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Release Conventions 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. Review the folder before installing.
What licence does Release Conventions use?
Release Conventions is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Conventions use?
About 893 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Release Conventions?
Skills that share tags, products or a category with Release Conventions: React Router Pull Request Creator (remix-run/react-router, 57k stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9.1k stars), Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars) and Git Conventions (werf/werf, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Conventions?
kveld9 (a GitHub user) maintains it in kveld9/kveld-morphe-patches, which has 113 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.
Source: kveld9/kveld-morphe-patches on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.