What is managing-project-releases?

A workflow for breaking a planned feature or release into GitHub issues written with Given/When/Then scenarios. This format describes a starting situation, an action, and the expected result.

Reading implementation plans, creating milestones, drafting feature, bug, or maintenance issues, defining acceptance scenarios and tests, and adding the issues to a GitHub Project board.

It turns broad release plans into smaller, ordered, testable tasks and keeps their dependencies, labels, milestone, and project-board placement organized.

How darkcofy/sqlprism configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to darkcofy/sqlprism. 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/darkcofy/sqlprism/main/.claude/skills/managing-project-releases/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/darkcofy/sqlprism

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/darkcofy/sqlprism/managing-project-releases/github.svg)](https://agentmods.dev/skills/darkcofy/sqlprism/managing-project-releases)

Your own site

<a href="https://agentmods.dev/skills/darkcofy/sqlprism/managing-project-releases"><img src="https://agentmods.dev/badge/skills/darkcofy/sqlprism/managing-project-releases/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/darkcofy/sqlprism/managing-project-releases"><img src="https://agentmods.dev/badge/skills/darkcofy/sqlprism/managing-project-releases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 600 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.00061	$0.00600
Opus 5.5	$0.00024	$0.00240
Sonnet 5.5	$0.00012	$0.00120
Haiku 4.5	$0.00006	$0.00060

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

Security

Grade A, and why

managing-project-releases 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.

.claude/skills/managing-project-releases/SKILL.md · 75 lines

What it actually says

Managing Project Releases

Context

GitHub repo: darkcofy/sqlprism
GitHub Project: SQLPrism (project number 1, owner darkcofy)
Labels: enhancement, bug, chore (no sizing labels)
Branch convention: feat-<name>, fix-<name>, chore-<name>

Workflow

Read the implementation plan for the release from .claude/plans/
Create a milestone named after the release version (e.g., v1.0.1)
Decompose into issues — one per logical unit of work
Write each issue in BDD format — see BDD-TEMPLATE.md
Add all issues to the GitHub Project board
Update dependency references with actual issue numbers after creation

Issue Decomposition Guidelines

Break work into issues that are:

Independent where possible — parallelizable steps get separate issues
Ordered by dependency — identify what blocks what
Testable — every issue has BDD scenarios that become test cases
Single responsibility — one issue = one logical change

Group by layer, not by file. Example layers:

Schema/migration changes
Renderer/parser changes
Core logic (indexer, engine)
API/tool surface (MCP tools, CLI commands)
Tests (can be a single issue or per-layer)

Creating Issues

gh issue create \
  --milestone "<version>" \
  --label "<type>" \
  --title "<concise title>" \
  --body "$(cat <<'EOF'
<BDD body — see BDD-TEMPLATE.md>
EOF
)"

After creating all issues, add them to the project:

gh project item-add 1 --owner darkcofy --url "<issue_url>"

Then update dependency cross-references to use actual issue numbers.

Creating Milestones

gh api repos/darkcofy/sqlprism/milestones \
  -f title="<version>" \
  -f description="<one-line summary>" \
  -f state="open"

Label Selection

Label	When to use
`enhancement`	New features, new capabilities
`bug`	Fixing broken behavior
`chore`	Migrations, CI, deps, refactors

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.

BDD-TEMPLATE.md 3.4 KB

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.

2mo ago First seen · 75 lines · 61 tokens per session scan A fd3fc5fcb4ea

Subscribe to this mod's changes

managing-project-releases is a skill published in the GitHub repository darkcofy/sqlprism (1 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 600 once invoked, about $0.0002 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-09-01.

Git and workflow Project management Releases

managing-project-releases next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
managing-project-releasesdarkcofy/sqlprism	Skill	1	4mo ago	Apache-2.0	A	61	Claude Code
release-announcementpaperclipai/paperclip	Skill	111k	yesterday	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	yesterday	Apache-2.0	A	22	Claude Code, Codex

sqlprism: Skill for Claude Code