Pump Build Release
nirholas/pump-fun-sdk
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…
Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata.
Install Prepare Rslint npm Release
$ npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install web-infra-dev/rslint prepare-rslint-npm-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/web-infra-dev/rslint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prepare-rslint-npm-release .claude/skills/prepare-rslint-npm-release && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prepare-rslint-npm-release" agent skill from https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-release into .claude/skills/prepare-rslint-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-rslint-npm-release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install web-infra-dev/rslint prepare-rslint-npm-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rslint.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/prepare-rslint-npm-release .agents/skills/prepare-rslint-npm-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prepare-rslint-npm-release" agent skill from https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-release into .agents/skills/prepare-rslint-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-rslint-npm-release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install web-infra-dev/rslint prepare-rslint-npm-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rslint.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/prepare-rslint-npm-release .cursor/skills/prepare-rslint-npm-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prepare-rslint-npm-release" agent skill from https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-release into .cursor/skills/prepare-rslint-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-rslint-npm-release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/web-infra-dev/rslint.git --path .agents/skills/prepare-rslint-npm-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install web-infra-dev/rslint prepare-rslint-npm-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rslint.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/prepare-rslint-npm-release .gemini/skills/prepare-rslint-npm-release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prepare-rslint-npm-release" agent skill from https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-release into .gemini/skills/prepare-rslint-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-rslint-npm-release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install web-infra-dev/rslint prepare-rslint-npm-releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/web-infra-dev/rslint.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/prepare-rslint-npm-release .github/skills/prepare-rslint-npm-release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prepare-rslint-npm-release" agent skill from https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-release into .github/skills/prepare-rslint-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-rslint-npm-release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install web-infra-dev/rslint prepare-rslint-npm-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/web-infra-dev/rslint.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/prepare-rslint-npm-release .opencode/skills/prepare-rslint-npm-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prepare-rslint-npm-release" agent skill from https://github.com/web-infra-dev/rslint/tree/main/.agents/skills/prepare-rslint-npm-release into .opencode/skills/prepare-rslint-npm-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-rslint-npm-release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
prepare-rslint-npm-release- GitHub stars
- 461
- Token cost
- ~1.5k tokens
- SKILL.md length
- 756 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata.
- Release preparation
- SKILL.md covers Establish the release state, Update versions and metadata, Review the generated diff and Deliver the preparation PR
- Calls pnpm and git
- Version bump PRs
What it does
Prepare Rslint npm Release is an agent skill from web-infra-dev/rslint. Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata. Use for release preparation or version bump PRs, not for publishing npm packages, canary releases, VS Code Marketplace releases, or the independent tsgo/Rust release line.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting and Deployment. It works with npm, TypeScript, Visual Studio Code and Rust. The repository describes itself as: High-performance, ESLint-compatible linter for JavaScript and TypeScript. The licence is MIT.
When your agent uses it
- Release preparation
- Version bump PRs
- Not for publishing npm packages
- Canary releases
Example prompts
- “/prepare-rslint-npm-release”
What it can do on your machine
Read from SKILL.md and the folder at commit bfe1710. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpmgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Prepare Rslint npm Release loads about 1.5k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 756 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from web-infra-dev/rslint at commit bfe1710, republished under its MIT licence (© web-infra-dev). 756 words, ~1,525 tokens.
Download SKILL.mdSave it as
.claude/skills/prepare-rslint-npm-release/SKILL.md (or your agent's skills folder).- name
- prepare-rslint-npm-release
- description
- Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata. Use for release preparation or version bump PRs, not for publishing npm packages, canary releases, VS Code Marketplace releases, or the independent tsgo/Rust release line.
Prepare an Rslint npm Release PR
Prepare a reviewable version and metadata PR, following the shape of
PR #2080. Use the current
pnpm sync:version-info command introduced in #2078; #2080 used the older
sync:rule-releases command and data filename.
Establish the release state
Follow the repository's AGENTS.md for branches and local verification. Read these current sources before choosing commands or file scope:
- scripts/version.mjs and the root package.json: version calculation and package selection.
- scripts/sync-version-info/: rule history and the pinned TypeScript commit/release mapping.
- Sync release information: the manual preparation sequence.
Resolve the intended stable version or major, minor, or patch bump from the
request. Ask for the target if it cannot be inferred. The version script bumps
from the highest base version in its selected manifests, so inspect those
versions before predicting the result.
Fetch the main branch and release tags. Determine the previous stable vX.Y.Z
tag, excluding prerelease tags, and check for an existing branch or PR for the
requested release. Start new preparation from current origin/main on a branch
such as chore/release-<version>; resume an existing release branch instead of
bumping again. If the target is already released, report that state rather than
silently choosing another version.
Update versions and metadata
Run commands from the repository root. For an agreed patch release:
pnpm run version patch
pnpm sync:version-infoUse the requested bump type in place of patch. If the intended version bump is
already present, skip the first command and review or refresh the metadata.
version is not idempotent: running it again advances the version again. A failed
metadata lookup is a reason to retry the sync after resolving the failure, not
to repeat the bump.
The version script owns the unified package selection: the root manifest,
packages/*/package.json except packages/tsgo/package.json, and
npm/rslint/*/package.json. This includes private workspace packages and the
VS Code extension manifest; updating that manifest is part of version alignment,
not a Marketplace release. Derive the current selection from the script rather
than hardcoding #2080's package count. Preserve workspace: dependency ranges.
The independent tsgo packages and Rust crate versions are outside this workflow.
The sync writes website/releases.json for the new stable version. It reads the
indexed typescript-go gitlink and queries upstream TypeScript tags. Record the
compiler already pinned for this release; preparing a release does not imply a
compiler upgrade. Stage any separately authorized submodule revision change
before syncing. The sync can read the pin without initializing the submodule.
The default sync skips when the package version equals the latest stable tag.
An unexpected skip during new release preparation is not successful generation:
check the package version and fetched tags. Use incremental sync for normal
preparation; full rebuilds historical rule records and belongs to a separate
history repair request.
Show full SKILL.md (315 more words)Show less
Review the generated diff
Check these invariants before committing:
- Every selected manifest has the intended version. Ordinary version changes
affect only its
versionfield; investigate unrelated dependency, script, formatting, or lockfile changes. - The new release appears once in
website/releases.json. Earlier records and compiler bindings are unchanged, and nomainentry or compiler backfill is introduced. - New rule IDs are unique and sorted. The list equals the registered rules added
since the previous stable release, excluding IDs recorded in earlier releases.
Cross-check implementations and the relevant core/plugin
all.goaggregators for both missing and spurious entries; a helper or fixture directory is not a rule. A release with no new rules is valid. typescript.commitequals the indexed gitlink.typescript.releaseVersionis an exact upstream tag match, including peeled annotated tags, ornullwhen no tag matches. Do not substitute the latest TypeScript release or a version reported by upstream source files.- A second
pnpm sync:version-inforun leaves the generated file unchanged.
For version and metadata-only changes, follow #2080's focused verification:
run pnpm run check-spell with every changed text path explicitly, run
pnpm run format:check, and run git diff --check. Apply AGENTS.md's affected
package rules if source or build behavior also changes. The generic build/test
suggestions printed by version.mjs are not a request for full local suites.
Deliver the preparation PR
Commit the version manifests and release metadata together, with a message and
PR title such as chore: release npm <version>. Push the release branch and open
a PR targeting main, or update the existing release PR. Include the version
transition, actual manifest count, new rule count, TypeScript binding, and the
verification commands/results. Keep temporary verification artifacts outside
the commit.
This workflow ends at the preparation PR. Actual publication is a separate
manual release.yml workflow; merging a
version PR does not publish npm packages. Its npm-only selection is
to_release=npm. Draft release notes, when requested, use the separate
create-draft-release-notes skill.
© web-infra-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/prepare-rslint-npm-release of web-infra-dev/rslint.
Open the folder on GitHubat commit bfe1710
Compare with similar skills
Prepare Rslint npm Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prepare Rslint npm Release this skillweb-infra-dev/rslint | 461 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Pump Build Releasenirholas/pump-fun-sdk | 133 | — | ~620 | Automated safety check: Pass | Custom licence | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.3k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Code Formatterjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Eslintmanagedcode/dotnet-skills | 486 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Htmlhintmanagedcode/dotnet-skills | 486 | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Code Formatter
jeremylongshore/tons-of-skills-marketplace
Execute automatically formats and validates code files using Prettier and other formatting tools.
Eslint
managedcode/dotnet-skills
Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets.
Htmlhint
managedcode/dotnet-skills
Use HTMLHint in .NET repositories that ship static HTML output or standalone frontend templates.
Webhint
managedcode/dotnet-skills
Use webhint in .NET repositories that ship browser-facing frontends.
More from web-infra-dev/rslint
Port Rule
web-infra-dev/rslint
Port a new ESLint core or plugin rule to rslint, including explicitly requested batches.
Debug CI
web-infra-dev/rslint
Reproduce Linux CI failures locally using Docker when the same tests pass on the host, especially Go platform differences and VS Code extension tests requiring xvfb.
Related
Categories
Questions about Prepare Rslint npm Release
What does Prepare Rslint npm Release do?
Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata. Prepare Rslint npm Release is an agent skill from web-infra-dev/rslint. Prepare a stable release PR for the unified rslint npm packages by updating package versions and rule/TypeScript release metadata.
When should I use Prepare Rslint npm Release?
Prepare Rslint npm Release fits situations like: release preparation; version bump PRs; not for publishing npm packages; canary releases.
How do I install Prepare Rslint npm Release in Claude Code?
Run `npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a claude-code`. Or copy the skill folder (.agents/skills/prepare-rslint-npm-release in web-infra-dev/rslint) into .claude/skills/prepare-rslint-npm-release in your project. Claude Code loads it when a task matches its description.
How do I install Prepare Rslint npm Release in Codex?
Run `npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a codex`. Or copy the skill folder (.agents/skills/prepare-rslint-npm-release in web-infra-dev/rslint) into .agents/skills/prepare-rslint-npm-release in your project. Codex loads it when a task matches its description.
Can I use Prepare Rslint npm Release in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add web-infra-dev/rslint --skill prepare-rslint-npm-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prepare-rslint-npm-release, .gemini/skills/prepare-rslint-npm-release, .github/skills/prepare-rslint-npm-release and .opencode/skills/prepare-rslint-npm-release in your project.
What does Prepare Rslint npm Release need to run?
Going by SKILL.md and its folder, Prepare Rslint npm Release needs the command-line tools its instructions call (pnpm and git).
Does Prepare Rslint npm Release access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Prepare Rslint npm Release safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Prepare Rslint npm Release use?
Prepare Rslint npm Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prepare Rslint npm Release use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Prepare Rslint npm Release?
Skills that share tags, products or a category with Prepare Rslint npm Release: Pump Build Release (nirholas/pump-fun-sdk, 133 stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Code Formatter (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Eslint (managedcode/dotnet-skills, 486 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prepare Rslint npm Release?
web-infra-dev (a GitHub organization) maintains it in web-infra-dev/rslint, which has 461 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.
Source: web-infra-dev/rslint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.