prepare-github-release
Skill8 starsChanged 45 days agoMITView on GitHub
Prepares a GitHub Release for RoslynMcpServer without git push or gh. Resolves the commit, csproj Version, commit messages since the previous v* tag (max 16), and the Actions Run workflow URL. Use when the user asks to выпусти релиз, пометь релизным, cut a release, tag a release commit, or prepare a GitHub Release.
- Commits and pushes
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/roslyn-mcp-build-sdk.mdcCursor rule
- .cursor/rules/roslyn-mcp-ci.mdcCursor rule
- .cursor/rules/roslyn-mcp-decompile.mdcCursor rule
- .cursor/rules/roslyn-mcp-dev-conventions.mdcCursor rule
- .cursor/rules/roslyn-mcp-docs-agents.mdcCursor rule
- .cursor/rules/roslyn-mcp-docs-lifecycle.mdcCursor rule
- .cursor/rules/roslyn-mcp-github-release.mdcCursor rule
- .cursor/rules/roslyn-mcp-overview.mdcCursor rule
- .cursor/rules/roslyn-mcp-paths.mdcCursor rule
- .cursor/rules/roslyn-mcp-pitfalls.mdcCursor rule
- .cursor/rules/roslyn-mcp-structural-tests.mdcCursor rule
- .cursor/rules/roslyn-mcp-tools.mdcCursor rule
- .cursor/rules/roslyn-mcp-version-bump.mdcCursor rule
- epoch-subagent-loopSkill
- epoch-subagent-loopSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 19
Only when the user explicitly asked to release.
- Very specific: line 30
Read this skill. Run from the repo root (PowerShell.
- Distinctive: line 38
Stop if the script throws or reports:
- Very specific: line 51
Do not create a local tag.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prepare GitHub Release
The agent cannot authenticate git push (SSH key passphrase). Do not tag,
push, or run gh release create. Actions creates the tag and Release after a
human workflow_dispatch.
When to run
Only when the user explicitly asked to release. Never after a normal merge, bugfix, or docs commit.
| User says | -CommitRef |
| выпусти / текущий / HEAD | HEAD (default) |
| предыдущий / прошлый коммит | HEAD~1 |
| SHA | that SHA |
Steps
- Read this skill. Run from the repo root (PowerShell; use
;not&&):
powershell -NoProfile -File .github/scripts/Get-ReleaseMetadata.ps1 -CommitRef HEADPass -Strict after the commit is already on origin/main and the change is not docs-only.
- Stop if the script throws or reports:
- On origin/main : False — user must
git pushthat commit themselves, then dispatch. - Docs-only : True — refuse a binary release (README in the zip is not a reason).
- Tag
v{Version}would collide with an already shipped version — they need a csproj bump first.
- On origin/main : False — user must
Reply with SHA,
v{Version}, notes preview, and:GitHub → Actions → Release → Run workflow
- Branch:
main commit_sha: the SHA from the script
Workflow URL is in the script output (
run_workflow_url).- Branch:
- Do not create a local tag. Actions will create
v{Version}on that SHA.
Notes
- Changelog: commit subjects (and bodies) since the previous
v*tag; newest 16 if there are more. - Batch bugfixes: wait until the last commit is on
main, then dispatch that SHA once. force=trueon the workflow is only for an intentional docs-only binary republish.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

