Borrowing it
Nothing to install: this file belongs to ishida-supsys/oretachi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ishida-supsys/oretachi/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/ishida-supsys/oretachiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ishida-supsys/oretachi/release)<a href="https://agentmods.dev/skills/ishida-supsys/oretachi/release"><img src="https://agentmods.dev/badge/skills/ishida-supsys/oretachi/release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ishida-supsys/oretachi/release"><img src="https://agentmods.dev/badge/skills/ishida-supsys/oretachi/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01269 |
| Opus 5.5 | $0.00000 | $0.00508 |
| Sonnet 5.5 | $0.00000 | $0.00254 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
バージョンをバンプし、CHANGELOG.md を更新してコミットする。
使い方
引数なし、または以下を指定:
patch/minor/major— バンプ種別1.2.3のような具体的なバージョン番号
手順
1. 現在バージョンと次バージョンを決定
package.json から現在バージョンを読み取る。
引数で明示的にバージョンが指定された場合はそれを使う。
引数がなければ git log を分析してバンプ種別を提案し、ユーザーに確認を取ってから進む:
BREAKING CHANGEまたはfeat!:/fix!:→ major バンプを提案feat:コミットがあれば → minor バンプを提案fix:/perf:のみ → patch バンプを提案- それ以外 → patch バンプを提案
提案時は以下の形式でユーザーに示す:
コミット分析の結果、minor バンプを提案します。
現在: 0.12.0 → 次バージョン: 0.13.0
よろしいですか？ (別のバージョンを指定することもできます)
ユーザーが承認または別バージョンを指定してから次のステップに進む。
2. git log を取得
git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --pretty=format:"%s"
コミットメッセージを以下のセクションに分類:
feat:→ Addedfix:→ Fixedperf:→ Changed (パフォーマンス改善)refactor:→ Changeddocs:→ Documentationci:/chore:/build:/test:→ Other (省略可)BREAKING CHANGE/!:→ 各セクション冒頭に ⚠️ で記載
コミット本文から重要な説明を抽出してリスト項目を簡潔に書く（英語または日本語、既存 CHANGELOG に合わせる）。
3. git remote URL を取得
git remote get-url origin
GitHub URL に変換（例: https://github.com/owner/repo）。SSH形式 ([email protected]:owner/repo.git) も変換する。
4. CHANGELOG.md を更新
taiki-e/parse-changelog が期待する Keep a Changelog 形式で書く。
CHANGELOG.md が存在しない場合は新規作成。存在する場合は ## [Unreleased] セクションの直後に新バージョンセクションを挿入。
フォーマット例:
# Changelog
All notable changes to this project will be documented in this file.
This project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
## [X.Y.Z] - YYYY-MM-DD
### Added
- 新機能の説明
### Fixed
- バグ修正の説明
### Changed
- 変更内容の説明
[Unreleased]: https://github.com/owner/repo/compare/X.Y.Z...HEAD
[X.Y.Z]: https://github.com/owner/repo/compare/OLD.VER...X.Y.Z
重要なルール:
- 末尾にバージョン比較リンクを追加・更新する
Merge branch '...'コミットは無視するchore: releaseやchore: bump versionコミットは無視する- セクションが空の場合はそのセクション見出しを省略する
- 今日の日付を使う
5. バージョン番号を3ファイルで更新
以下の3ファイルのバージョン文字列を新バージョンに書き換える:
package.json—"version": "X.Y.Z"src-tauri/Cargo.toml—version = "X.Y.Z"(package セクション)src-tauri/tauri.conf.json—"version": "X.Y.Z"
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 134 lines · 0 tokens per session scan A 830f4dcf851f
release is a skill published in the GitHub repository ishida-supsys/oretachi (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,269 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
bump-version
Use when preparing a Sessions Chronicle release that needs synchronized version metadata updates and Flatpak build verification, especially when release notes are missing and need a reviewed draft.
ship
Fully automated ship workflow. Merges the base branch, runs tests, audits coverage, reviews the diff, generates a CHANGELOG entry, bumps the version, commits, pushes, and creates the PR. Use when asked to "ship", "create a PR", or "open a pull request".
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
dsh-plugin-publisher
A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.