القائمة
Dry run for release: summarize changes since last release and suggest version bump.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/dyoshikawa/rulesync --skill release-dry-runيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Clear the open issue backlog and then cut a release, in one autonomous run: use the `batch-all-issues` skill to resolve every open issue, then the `goal-release` skill to draft, merge, and see the release through publication. Never asks the user anything — every decision is made autonomously, and blockers are reported at the end instead of interrupting the run.
Maps rulesync feature implementations to upstream coding-agent documentation. Use when evaluating rulesync issues, comparing any coding-agent client with rulesync source capability surfaces, checking support, or planning a client map.
Research recent upstream releases of every rulesync target tool, detect capabilities rulesync has not yet followed, file one GitHub issue per tool for the gaps, and scout popular or promising coding agents rulesync does not target yet.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | release-dry-run |
| description | Dry run for release: summarize changes since last release and suggest version bump. |
| targets | ["*"] |
This is a dry run command for release. It will summarize the changes since the last release and suggest the appropriate version bump based on semantic versioning.
Get the latest release tag.
git fetch --tags to ensure all tags are available.git describe --tags --abbrev=0 to get the latest tag.Compare code changes between the latest tag and the current HEAD.
git log ${latest_tag}..HEAD --oneline to get the commit list.git diff ${latest_tag}..HEAD --stat to get the file change statistics.Analyze the changes and create a summary in the following format:
## Changes Summary
### Commits since ${latest_tag}
- List of commits with their messages
### Changed Files
- Summary of file changes (added, modified, deleted)
### Change Categories
- **Breaking Changes**: List any breaking changes (API changes, removed features, etc.)
- **New Features**: List new features added
- **Bug Fixes**: List bug fixes
- **Other Changes**: List other changes (refactoring, documentation, tests, etc.)
Based on the analysis, suggest the appropriate version bump following semantic versioning rules:
Important: Whenever the changes include any feature removal or a change in the behavior of an existing feature, do not hesitate to choose a MAJOR version bump. Prioritize protecting users from unexpected breakage over keeping the version number low.
Output the final recommendation in the following format:
## Version Bump Recommendation
Current version: ${latest_tag}
Recommended bump: MAJOR / MINOR / PATCH
Suggested new version: vX.Y.Z
### Reasoning
- Explain why this version bump is recommended based on the changes.
Note: This is a dry run only. No files will be modified and no commits will be made.