How do I install the Pump Build Release skill?

Run npx skillmds add solizardking/pump-build-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pump Build Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pump Build Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pump Build Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pump Build Release?

Solizardking (@solizardking) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pump Build Release by solizardking — Agent Skill

Name: Pump Build Release
Rating: 4.2 (5 reviews)
Author: Solizardking

Pump Build Release

Run and maintain Pump.fun SDK build, release, and publishing workflows across TypeScript, Rust, npm, Vercel, Makefile targets, linting, semantic release, and MCP server distribution. Use when preparing or debugging Pump.fun package releases.

Solizardking ecc0526 2.5 KB Updated Sep 9, 2026 0 repo stars

File contents

Build & Release — SDK Build Pipeline & Publishing

Build and release the Pump SDK ecosystem: tsup TypeScript builds, Cargo release profiles, semantic release, npm publishing, and deployment.

SDK Build Pipeline (TypeScript)

npx tsup src/index.ts --format cjs,esm --dts

Output: dist/index.cjs, dist/index.mjs, dist/index.d.ts

Rust Release Profile

[profile.release]
opt-level = 3
lto = true
codegen-units = 1
strip = true

Semantic Release with Commitizen

Commit format: type(scope): description

Type	Effect
`feat:`	Minor version bump
`fix:`	Patch version bump
`feat!:` or `BREAKING CHANGE:`	Major version bump
`chore:`, `docs:`, `style:`	No release

Makefile Targets

Target	Description
`make build`	Build SDK + Rust binary
`make test`	Run all tests
`make bench`	Run benchmarks
`make lint`	Run all linters
`make clean`	Clean build artifacts
`make release`	Build release binary

Linting

Tool	Language	Config
ESLint/tsup	TypeScript	`tsconfig.json`
`cargo clippy`	Rust	Default warnings
`cargo fmt`	Rust	`rustfmt.toml`
ShellCheck	Bash	Default rules

npm Publishing

npm publish --access public
# Package: @nirholas/pump-sdk

Vercel Website Deployment

# website/ directory — static HTML/CSS/JS
vercel --prod

MCP Server Distribution

npm publish --access public
# Package: @pump-fun/mcp-server
# Usage: npx -y @pump-fun/mcp-server

Patterns to Follow

Use conventional commits for automated changelog generation
Run cargo clippy and cargo fmt before every Rust commit
Build TypeScript with both CJS and ESM output
Test release builds before publishing
Pin dependencies with lockfiles

Common Pitfalls

tsup may not pick up all type exports — verify .d.ts output
cargo build --release takes significantly longer than debug builds
npm prepublishOnly scripts should run tests and lint
Vercel deployment requires matching Node.js version

---name: pump-build-releasedescription: Run and maintain Pump.fun SDK build, release, and publishing workflows across TypeScript, Rust, npm, Vercel, Makefile targets, linting, semantic release, and MCP server distribution. Use when preparing or debugging Pump.fun package releases.--- # Build & Release — SDK Build Pipeline & Publishing Build and release the Pump SDK ecosystem: tsup TypeScript builds, Cargo release profiles, semantic release, npm publishing, and deployment. ## SDK Build Pipeline (TypeScript) ```bash npx tsup src/index.ts --format cjs,esm --dts ``` Output: `dist/index.cjs`, `dist/index.mjs`, `dist/index.d.ts` ## Rust Release Profile ```toml [profile.release] opt-level = 3 lto = true codegen-units = 1 strip = true ``` ## Semantic Release with Commitizen Commit format: `type(scope): description` | Type | Effect | |------|--------| | `feat:` | Minor version bump | | `fix:` | Patch version bump | | `feat!:` or `BREAKING CHANGE:` | Major version bump | | `chore:`, `docs:`, `style:` | No release | ## Makefile Targets | Target | Description | |--------|-------------| | `make build` | Build SDK + Rust binary | | `make test` | Run all tests | | `make bench` | Run benchmarks | | `make lint` | Run all linters | | `make clean` | Clean build artifacts | | `make release` | Build release binary | ## Linting | Tool | Language | Config | |------|----------|--------| | ESLint/tsup | TypeScript | `tsconfig.json` | | `cargo clippy` | Rust | Default warnings | | `cargo fmt` | Rust | `rustfmt.toml` | | ShellCheck | Bash | Default rules | ## npm Publishing ```bash npm publish --access public # Package: @nirholas/pump-sdk ``` ## Vercel Website Deployment ```bash # website/ directory — static HTML/CSS/JS vercel --prod ``` ## MCP Server Distribution ```bash npm publish --access public # Package: @pump-fun/mcp-server # Usage: npx -y @pump-fun/mcp-server ``` ## Patterns to Follow - Use conventional commits for automated changelog generation - Run `cargo clippy` and `cargo fmt` before every Rust commit - Build TypeScript with both CJS and ESM output - Test release builds before publishing - Pin dependencies with lockfiles ## Common Pitfalls - `tsup` may not pick up all type exports — verify `.d.ts` output - `cargo build --release` takes significantly longer than debug builds - npm `prepublishOnly` scripts should run tests and lint - Vercel deployment requires matching Node.js version

Frequently asked questions