تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

$pwd:

draft-release

Name: Draft Release
Author: dyoshikawa

// Draft a new release of the project.

تشغيل في Manus

$ git log --oneline --stat

stars:١٬١٣٢

forks:١٢١

updated:٣٠ مارس ٢٠٢٦ في ٠٦:٠٠

SKILL.md

readonly

name	draft-release
description	Draft a new release of the project.
targets	["*"]

First, let's work on the following steps.

Confirm that you are currently on the main branch and pull the latest changes. If not on main branch, switch to main branch.
Compare code changes between the previous version tag and the latest commit to prepare the release description.

Write in English.
Do not include confidential information.
Sections, What's Changed, Contributors and Full Changelog are needed.
./tmp/release-notes/*.md will be used as the release notes.

Then, from $ARGUMENTS, get the new version without v prefix, and assign it to $new_version. For example, if $ARGUMENTS is "v1.0.0", the new version is "1.0.0".

If $ARGUMENTS is empty, determine the new version automatically by performing the release-dry-run skill.

Let's resume the release process.

Run git pull.
Run git checkout -b release/v${new_version}.
Update getVersion() function to return the ${new_version} in src/cli/index.ts, and run pnpm cicheck. If the checks fail, fix the code until pass. Then, execute git add, git commit and git push.
Update the version with pnpm version ${new_version} --no-git-tag-version.
Since package.json will be modified, execute git commit and git push.
As a precaution, verify that getVersion() in src/cli/index.ts is updated to the ${new_version}.
Run gh pr create to the main branch.
Create a draft release using gh release create v${new_version} --draft --title v${new_version} --notes-file ./tmp/release-notes/*.md command on the github.com/dyoshikawa/rulesync repository. This creates a draft release so that the publish-assets workflow can upload assets later.

related-skills.json

نفس المستودع

rulesync.md

from "dyoshikawa/rulesync"

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

2026-05-291.1k

rulesync-feature-research.md

from "dyoshikawa/rulesync"

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.

2026-05-181.1k

skill-creator.md

from "dyoshikawa/rulesync"

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

2026-04-011.1k

create-issue.md

from "dyoshikawa/rulesync"

Create a GitHub issue with detailed description, purpose, and appropriate labels

2026-03-301.1k

release-dry-run.md

from "dyoshikawa/rulesync"

Dry run for release: summarize changes since last release and suggest version bump.

2026-03-301.1k

security-scan-diff.md

from "dyoshikawa/rulesync"

Scan for malicious code in git diff between a tag/commit and HEAD

2026-03-301.1k

package.json

"author": "dyoshikawa"

"repository": "dyoshikawa/rulesync"

فتح مستودع GitHub عرض مستودعات المنشئ

$ install --global

$ download --local

تشغيل في Manus

$ useful --forSOC

مطوّرو البرمجياتمهن الحاسوب والرياضيات15-1252L4

name	draft-release
description	Draft a new release of the project.
targets	["*"]

First, let's work on the following steps.

Confirm that you are currently on the main branch and pull the latest changes. If not on main branch, switch to main branch.
Compare code changes between the previous version tag and the latest commit to prepare the release description.

Write in English.
Do not include confidential information.
Sections, What's Changed, Contributors and Full Changelog are needed.
./tmp/release-notes/*.md will be used as the release notes.

Then, from $ARGUMENTS, get the new version without v prefix, and assign it to $new_version. For example, if $ARGUMENTS is "v1.0.0", the new version is "1.0.0".

If $ARGUMENTS is empty, determine the new version automatically by performing the release-dry-run skill.

Let's resume the release process.

Run git pull.
Run git checkout -b release/v${new_version}.
Update getVersion() function to return the ${new_version} in src/cli/index.ts, and run pnpm cicheck. If the checks fail, fix the code until pass. Then, execute git add, git commit and git push.
Update the version with pnpm version ${new_version} --no-git-tag-version.
Since package.json will be modified, execute git commit and git push.
As a precaution, verify that getVersion() in src/cli/index.ts is updated to the ${new_version}.
Run gh pr create to the main branch.
Create a draft release using gh release create v${new_version} --draft --title v${new_version} --notes-file ./tmp/release-notes/*.md command on the github.com/dyoshikawa/rulesync repository. This creates a draft release so that the publish-assets workflow can upload assets later.

draft-release

المزيد من هذا المستودع

المزيد من هذا المستودع