Menu
Check, build, and publish the package to npm with pnpm
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/fabis94/fabis-ralph-loop --skill publishThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Generate a Product Requirements Document for a new feature. Use when planning a feature, starting a new project, or asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Convert an existing PRD into prd.json format for Ralph autonomous agent execution. Use when you have a PRD and want to run it through the Ralph loop. Triggers on: convert this prd, turn this into ralph format, create prd.json, ralph json.
Update the fabis-ralph-loop.config.ts configuration file. Use when adding backpressure commands, changing container settings, updating project metadata, or modifying any Ralph loop config. Triggers on: update ralph config, add backpressure command, change container settings, modify ralph-loop config.
Showing SKILL.md
| name | publish |
| description | Check, build, and publish the package to npm with pnpm |
| userInvocable | true |
| argumentHint | [--dry-run] |
| allowedTools | {"claude":["Bash","Read","Grep","Glob","AskUserQuestion"]} |
Check, build, and publish this package to npm using pnpm.
Parse $ARGUMENTS for:
--dry-run — run all steps but use --dry-run for the actual publishRun ALL checks upfront before doing any work. If any check fails, stop immediately and print the remediation instructions.
Check in order:
npm whoami — currently logged in[ -n "$NPM_TOKEN" ] || [ -n "$NODE_AUTH_TOKEN" ]If neither is available, stop and tell the user:
NPM authentication is required for publishing packages. Set up one of:
- Run
npm loginfor interactive npm login- Set
export NPM_TOKEN=<token>with an npm access token- Add
//registry.npmjs.org/:_authToken=<token>to.npmrcCreate a token at: https://www.npmjs.com/settings/~/tokens
Read package.json and verify these fields are present and non-empty:
repository — must be set (string or object with url). Required for npm package linking.files — must be a non-empty array. Required to control what gets published to npm.If either is missing, stop and tell the user which fields need to be added.
git status — working directory must be clean (no uncommitted changes)Run the full check suite:
pnpm check
This runs lint, format check, unused exports check, and tests. If any step fails, stop and fix the issue before continuing. Do not proceed to build if checks fail.
pnpm build
Verify the build succeeds without errors.
Present the user with a summary before publishing:
package.json)Ask the user to confirm before continuing.
pnpm publish [--dry-run] --no-git-checks
For scoped packages (@scope/name), use --access public if this is the first publish.
Print a summary:
https://www.npmjs.com/package/<name>)
Based on SOC occupation classification