pre-release
Skill656 starsChanged 7 months agoMITView on GitHub
Automates release preparation for throttled-py. Triggers when user message contains: - "release vX.Y.Z" with a GitHub release draft URL - "release vX.Y.Z" followed by changelog content Tasks: update version numbers, sync CHANGELOG_EN.rst and CHANGELOG.rst, run dependency sync.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- nrflo/nrflotheir own version, first seen Oct 29, 2026
- Cosmian/kmstheir own version, first seen Oct 8, 2026
- paiml/aprendertheir own version, first seen Oct 8, 2026
- mattpocock/sandcastletheir own version, first seen Oct 8, 2026
- rusq/slackdumptheir own version, first seen Jun 12, 2026
- marcfargas/skillstheir own version, first seen Feb 15, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- mattpocock/sandcastle★ 9.1ksame name
- rusq/slackdump★ 2.9ksame name
- Cosmian/kms★ 378same name
- paiml/aprender★ 141same name
- marcfargas/skills★ 4same name
- nrflo/nrflo★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 41
Release Date: Use today's date (YYYY-MM-DD)
- Distinctive: line 46
If URL provided: Fetch content from the release draft URL
- Distinctive: line 47
If content provided: Use the changelog content directly
- Distinctive: line 48
If neither accessible: Ask user to provide the content
- Distinctive: line 52
Update version string in these files:
- Very specific: line 77
Reference: Read .github/release-drafter-config.yml for:
- Very specific: line 126
Run the following command to update uv.lock:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pre-Release Workflow
{REPO}=https://github.com/ZhuoZhuoCrayon/throttled-py
Input Format
# With release draft URL
release v3.2.0 {REPO}/releases/tag/untagged-xxxxx
# With changelog content directly
release v3.2.0
<paste release draft content here>Workflow Overview
flowchart TD
A[Parse Input] --> B[Get Release Changelog]
B --> C[Update Version Numbers]
C --> D[Update CHANGELOG_EN.rst]
D --> E[Translate & Update CHANGELOG.rst]
E --> F[Sync Dependencies]
F --> G[Verification]Step 1: Parse Input
Extract from user input:
- Version:
vX.Y.Z→X.Y.Z - Release Date: Use today's date (
YYYY-MM-DD) - Changelog: From URL or directly provided content
Step 2: Get Release Changelog
- If URL provided: Fetch content from the release draft URL
- If content provided: Use the changelog content directly
- If neither accessible: Ask user to provide the content
Step 3: Update Version Numbers
Update version string in these files:
| File | Location |
pyproject.toml | version = "X.Y.Z" |
throttled/__init__.py | __version__ = "X.Y.Z" |
throttled/asyncio/__init__.py | __version__ = "X.Y.Z" |
Step 4: Update CHANGELOG_EN.rst
Insert new entry after the title section:
vX.Y.Z - YYYY-MM-DD
---------------------
`简体中文 (vX.Y.Z) <{GITHUB_REPOSITORY}/blob/main/CHANGELOG.rst#vxyz---YYYY-MM-DD>`_ | English
**{emoji} {category_title}**
- {change_entries}
**Full Changelog**: {GITHUB_REPOSITORY}/compare/vPREV...vX.Y.ZReference: Read .github/release-drafter-config.yml for:
- Category titles and their emojis
- Entry format template
Step 5: Translate & Update CHANGELOG.rst
Insert translated entry after the title section:
vX.Y.Z - YYYY-MM-DD
---------------------
`English Documents Available (vX.Y.Z) <{GITHUB_REPOSITORY}/blob/main/CHANGELOG_EN.rst#vxyz---YYYY-MM-DD>`_ | 简体中文
**{emoji} {category_title_zh}**
- {translated_change_entries}
**完整更新日志**: {GITHUB_REPOSITORY}/compare/vPREV...vX.Y.ZTranslation Reference
| EN Category | ZH Category |
| Breaking Changes | 破坏性变更 |
| New Features | 功能 |
| Improvements | 优化 |
| Bug Fixes | Bug 修复 |
| Dependencies | 依赖项更新 |
| Documentation | 文档 |
| Tests | 测试 |
| Maintenance | 维护工作 |
Common Translations
| English | Chinese |
| add / add support for | 添加 / 添加对 ... 的支持 |
| fix / resolve | 修复 |
| update / improve / optimize | 更新 / 改进 / 优化 |
| implement | 实现 |
| remove | 移除 |
| refactor | 重构 |
Note: Preserve technical terms, @author mentions, and PR numbers.
Step 6: Sync Dependencies
Run the following command to update uv.lock:
uv lockThis ensures uv.lock reflects the updated version in pyproject.toml.
Step 7: Verification
- Version numbers consistent across all 3 files
uv.lockupdated successfully- Cross-references between EN/ZH changelogs are correct
- RST anchor format:
#vxyz---YYYY-MM-DD(no dots, lowercase) - All categories from release draft included
- Only include sections that have content
- CRITICAL At the beginning of the verification summary, include:
✓ Conducted skill defined in
.agents/skills/pre-release/SKILL.md.
Format Reference
Refer to existing entries in CHANGELOG.rst and CHANGELOG_EN.rst for exact formatting.
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.

