Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

release

Estrelas3

Forks0

Atualizado3 de janeiro de 2026 às 23:03

Build, bump version, commit, and push a brain-jar plugin release. Usage: /release <plugin-name> <patch|minor|major> [message]

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

designnotdrum

designnotdrum/brain-jar

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	release
description	Build, bump version, commit, and push a brain-jar plugin release. Usage: /release <plugin-name> <patch\|minor\|major> [message]

Release Skill for brain-jar Plugins

Automates the full release cycle for a brain-jar plugin:

Build and typecheck
Bump version using semver
Update all version references
Commit with standard message
Push to remote

Usage

/release shared-memory patch "fix dependency issue"
/release shared-memory minor "add new feature"
/release perplexity-search major "breaking API change"

Procedure

1. Parse Arguments

Extract from the user's command:

plugin: The plugin name (e.g., shared-memory, perplexity-search)
bump: Version bump type (patch, minor, or major)
message: Optional commit message description

2. Validate Plugin Exists

Check that plugins/<plugin>/package.json exists. If not, error out.

3. Build and Typecheck

cd plugins/<plugin>
npm run build
npm run typecheck

If either fails, stop and report the error.

4. Calculate New Version

Read current version from plugins/<plugin>/package.json.

Apply semver bump:

patch: 1.2.3 -> 1.2.4
minor: 1.2.3 -> 1.3.0
major: 1.2.3 -> 2.0.0

5. Update All Version References

Update these files with the new version (same commit):

plugins/<plugin>/package.json - "version": "X.Y.Z"
plugins/<plugin>/.claude-plugin/plugin.json - "version": "X.Y.Z"
plugins/<plugin>/src/index.ts - version: 'X.Y.Z' in McpServer config
.claude-plugin/marketplace.json - version for this plugin
README.md - version in plugins table AND highlights section (see below)

5a. README Highlights Section

Check if a highlights section exists for this plugin:

Look for ### <plugin> highlights (vX.Y.Z) in README.md

If section exists: Update the version in the heading.

If section doesn't exist: Create one after the plugins table:

### <plugin> highlights (vX.Y.Z)

- **<feature from message>** - <brief description based on commit message>

For subsequent releases, add new bullet points to the existing section describing what changed (based on the commit message provided).

The highlights section should be concise - 3-5 bullet points max covering the most important features/fixes.

6. Rebuild and Bundle After Version Update

cd plugins/<plugin>
npm run build

Then from the repo root, rebuild all bundles:

cd /path/to/brain-jar
npm run bundle

This ensures both dist/index.js and dist/bundle.js have the updated code. The bundle is what marketplace installs actually load.

7. Stage and Commit

git add -A
git commit -m "<type>(<plugin>): <message>

<longer description if needed>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"

Commit type based on bump:

patch -> fix
minor -> feat
major -> feat! (breaking)

8. Push

git push

9. Report Success

Output:

Old version -> New version
Files updated
Commit hash
Remote push status

Example Output

Released shared-memory v1.3.2 -> v1.4.0

Updated files:
  - plugins/shared-memory/package.json
  - plugins/shared-memory/.claude-plugin/plugin.json
  - plugins/shared-memory/src/index.ts
  - .claude-plugin/marketplace.json
  - README.md

Commit: abc123f
Pushed to origin/main

Mais deste repositório

mesmo repositório

setup-chess-timer-hooks

designnotdrum/brain-jar

Install hookify rules for automatic chess timer session management

2026-01-193

create-adapter

designnotdrum/brain-jar

Create a custom source adapter for pattern-radar

2026-01-043

capture

designnotdrum/brain-jar

Capture thinking visually during brainstorming, architecture discussions, or explaining flows. Creates persistent Mermaid diagrams.

2026-01-043

using-perplexity-for-context

designnotdrum/brain-jar

Automatically use Perplexity search for personalized context enrichment. Use when facing unfamiliar technologies, decision points, learning questions, or preference-dependent choices.

2026-01-043

managing-memory

designnotdrum/brain-jar

Guide for storing enriched memories that capture decisions, preferences, and context. Use when making significant decisions or learning user preferences.

2026-01-043

pattern-radardigest

designnotdrum/brain-jar

Get your personalized trend briefing based on profile domains.

2026-01-043

name	release
description	Build, bump version, commit, and push a brain-jar plugin release. Usage: /release <plugin-name> <patch\|minor\|major> [message]

Release Skill for brain-jar Plugins

Automates the full release cycle for a brain-jar plugin:

Build and typecheck
Bump version using semver
Update all version references
Commit with standard message
Push to remote

Usage

/release shared-memory patch "fix dependency issue"
/release shared-memory minor "add new feature"
/release perplexity-search major "breaking API change"

Procedure

1. Parse Arguments

Extract from the user's command:

plugin: The plugin name (e.g., shared-memory, perplexity-search)
bump: Version bump type (patch, minor, or major)
message: Optional commit message description

2. Validate Plugin Exists

Check that plugins/<plugin>/package.json exists. If not, error out.

3. Build and Typecheck

cd plugins/<plugin>
npm run build
npm run typecheck

If either fails, stop and report the error.

4. Calculate New Version

Read current version from plugins/<plugin>/package.json.

Apply semver bump:

patch: 1.2.3 -> 1.2.4
minor: 1.2.3 -> 1.3.0
major: 1.2.3 -> 2.0.0

5. Update All Version References

Update these files with the new version (same commit):

plugins/<plugin>/package.json - "version": "X.Y.Z"
plugins/<plugin>/.claude-plugin/plugin.json - "version": "X.Y.Z"
plugins/<plugin>/src/index.ts - version: 'X.Y.Z' in McpServer config
.claude-plugin/marketplace.json - version for this plugin
README.md - version in plugins table AND highlights section (see below)

5a. README Highlights Section

Check if a highlights section exists for this plugin:

Look for ### <plugin> highlights (vX.Y.Z) in README.md

If section exists: Update the version in the heading.

If section doesn't exist: Create one after the plugins table:

### <plugin> highlights (vX.Y.Z)

- **<feature from message>** - <brief description based on commit message>

For subsequent releases, add new bullet points to the existing section describing what changed (based on the commit message provided).

The highlights section should be concise - 3-5 bullet points max covering the most important features/fixes.

6. Rebuild and Bundle After Version Update

cd plugins/<plugin>
npm run build

Then from the repo root, rebuild all bundles:

cd /path/to/brain-jar
npm run bundle

This ensures both dist/index.js and dist/bundle.js have the updated code. The bundle is what marketplace installs actually load.

7. Stage and Commit

git add -A
git commit -m "<type>(<plugin>): <message>

<longer description if needed>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"

Commit type based on bump:

patch -> fix
minor -> feat
major -> feat! (breaking)

8. Push

git push

9. Report Success

Output:

Old version -> New version
Files updated
Commit hash
Remote push status

Example Output

Released shared-memory v1.3.2 -> v1.4.0

Updated files:
  - plugins/shared-memory/package.json
  - plugins/shared-memory/.claude-plugin/plugin.json
  - plugins/shared-memory/src/index.ts
  - .claude-plugin/marketplace.json
  - README.md

Commit: abc123f
Pushed to origin/main