What is release-scope?

A release-planning guide that examines changes since the last version tag and decides whether to release the library, the desktop app, both, or neither. It does not change versions or publish anything.

Use it before releasing to choose the release type and determine whether to update the Dari library version, the Dari desktop version, or both.

It prevents releases from covering the wrong part of the product and avoids relying only on commit messages, which may not show which product area changed.

How easyhooon/dari configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to easyhooon/dari. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/easyhooon/dari/main/.claude/skills/release-scope/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/easyhooon/dari

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/easyhooon/dari/release-scope/github.svg)](https://agentmods.dev/skills/easyhooon/dari/release-scope)

Your own site

<a href="https://agentmods.dev/skills/easyhooon/dari/release-scope"><img src="https://agentmods.dev/badge/skills/easyhooon/dari/release-scope/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/easyhooon/dari/release-scope"><img src="https://agentmods.dev/badge/skills/easyhooon/dari/release-scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 168 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,327 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00168	$0.02327
Opus 5.5	$0.00067	$0.00931
Sonnet 5.5	$0.00034	$0.00465
Haiku 4.5	$0.00017	$0.00233

Measured 3d ago against content hash af100368b844, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-scope 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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/release-scope.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/release-scope/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

릴리스 범위 판정

gradle/libs.versions.toml의 dari(라이브러리, Maven Central)와 dariDesktop(데스크톱 앱, GitHub 릴리스)은 같은 번호 줄을 쓴다. 이 스킬은 마지막 릴리스 이후 바뀐 파일을 보고 둘 중 무엇을 올려야 하는지 정한다. 판정만 하고 파일은 바꾸지 않는다.

인자

base_tag (선택): 비교 기준 태그. 생략하면 가장 최근 x.y.z 태그.
ref (선택): 릴리스할 커밋. 생략하면 origin/main (릴리스는 main에서 태그를 만들기 때문).

절차

1. 스크립트 실행

.claude/skills/release-scope/scripts/release-scope.sh [base_tag] [ref]

확인: 출력 첫 줄의 Range:가 의도한 구간인지 본다. 기준 태그가 예상과 다르면(예: 핫픽스 태그가 따로 있음) 태그를 인자로 직접 넘겨 다시 실행한다.
이 단계가 끝나야 2단계로 간다. 판정을 스크립트 없이 git log만 보고 정하지 않는다. 이유: 커밋 메시지는 fix:여도 라이브러리 파일을 건드릴 수 있고, 판정 기준은 파일 경로다.

2. 판정 읽기

스크립트의 VERDICT는 영역별 변경으로 정해진다(위에서부터 먼저 걸리는 것).

VERDICT	조건	올릴 버전	Maven
`full`	`dari`, `dari-core`, `dari-noop`, `dari-runtime`, `dari-inspector-protocol`의 main 코드 변경, `dari-gradle-plugin`의 main 코드·빌드 파일 변경	`dari`와 `dariDesktop` 둘 다	배포
`desktop`	`dari-desktop-app`만 변경	`dariDesktop`만	건너뜀
`review`	공유 빌드 파일(`build.gradle.kts`, `gradle/`, 버전 외 카탈로그 줄 등)만 변경	3단계에서 판단	판단
`none`	문서, 샘플, 테스트, CI, 패키징 도구만 변경	없음	없음

test(테스트만), desktop-tooling(패키징 스크립트·데스크톱 워크플로)은 그 자체로는 릴리스 사유가 아니다. 다음 릴리스를 만들 때 반영된다.
카탈로그에서 dari/dariDesktop 줄만 바뀐 것(직전 릴리스의 버전 올림)은 변경으로 세지 않는다.
출력에 dariDesktop=<not split yet, follows dari>가 보이고 판정이 desktop이면: 그 ref에는 데스크톱 버전 분리(#158)가 아직 없다. /release desktop은 dariDesktop 키가 main에 있어야 동작하므로, 분리를 먼저 머지하라고 안내하거나 정식 릴리스로 진행할지 사용자에게 묻는다. 이유: 키 없이 데스크톱 전용으로 내면 설치 파일 버전과 태그가 어긋나 릴리스 워크플로가 실패한다.

3. 사람 판단이 필요한 경우만 처리

review이거나 Check: shared build files changed too가 나오면: 해당 파일의 diff를 열어, 바뀐 의존성·설정이 라이브러리 모듈에 적용되는지 본다. 라이브러리에 적용되면 full, 데스크톱에만 적용되면 desktop, 둘 다 아니면 none.
WARNING: InspectorProtocol.VERSION changed가 나오면: full이고, 앱과 데스크톱이 모두 업데이트해야 서로 연결된다. 릴리스 노트 Behavior changes에 반드시 적는다. 이유: 호환성은 이 값으로만 판단하므로, 한쪽만 올린 사용자는 연결이 끊긴다.
Note: feat commits present가 나오면: 사용자 관점에서 새 기능이면 minor, 고침뿐이면 patch를 제안한다. 버전 번호는 사용자가 정한다.

Read the full file on GitHub · 87 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/release-scope.sh 4.7 KB runs code

Changes

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.

3d ago First seen · 87 lines · 168 tokens per session scan A af100368b844

Subscribe to this mod's changes

release-scope is a skill published in the GitHub repository easyhooon/dari (38 stars, last pushed today), licensed Apache-2.0. It adds 168 tokens to every session and 2,327 once invoked, about $0.0007 per session on Opus 5.5. 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-10-26.

Git and workflow Planning Releases android android-library bridge debugger kotlin webview

release-kotlin-library

Use when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and API snapshots, and checking publication.

chrisbanes/skills · 46 tokens

release-new-version

Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).

niki914/zafiro · 54 tokens

findeck-release

A document-review workflow that works on one specification document and only the higher-level or reference documents configured for it. It supports reference and revise actions and records history with reference-specific snapshots.

fainaltn/findeck · 71 tokens

shepherd

Use when asked to shepherd, babysit, monitor, or poll open pull requests or merge requests, including triaging review feedback, CI failures, and routine follow-up.

chrisbanes/skills · 37 tokens

deliver-spec

Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.

chrisbanes/skills · 33 tokens

install-skill-from-github

Install a skill from a public GitHub repository onto this device. Use whenever the user pastes a GitHub URL or names a repo and wants a skill installed, imported, or updated, or asks to add a skill from GitHub — even if they only send a link. Covers finding SKILL.md in a repo, downloading it with python, and placing…

niki914/zafiro · 85 tokens

dari: Skill for Claude Code