Skip to content

x402agent/SolanaOS / skills/pump-build-release

pump-build-release

Verified

Build and release pipeline for the Pump SDK — tsup TypeScript builds, Cargo release profiles, semantic release with commitizen, npm publishing, linting, Makefile targets, Vercel deployment, and MCP server distribution.

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

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

Makefile Targets

TargetDescription
make buildBuild SDK + Rust binary
make testRun all tests
make benchRun benchmarks
make lintRun all linters
make cleanClean build artifacts
make releaseBuild release binary

Linting

ToolLanguageConfig
ESLint/tsupTypeScripttsconfig.json
cargo clippyRustDefault warnings
cargo fmtRustrustfmt.toml
ShellCheckBashDefault 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
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall