mindforge
MindForge publishes a Claude Code skill to the npm registry or private registry after performing comprehensive validation checks. Use this skill when you have completed development of a skill and are ready to release it publicly, ensuring the skill passes all validation levels, has proper documentation, and hasn't been previously published at the specified version.
git clone --depth 1 https://github.com/sairam0424/MindForge /tmp/mindforge && cp -r /tmp/mindforge/.agent/mindforge/publish- ~/.claude/skills/mindforgepublish-skill.md
# MindForge — Publish Skill Command
# Usage: /mindforge:publish-skill [skill-dir] [--registry URL] [--dry-run]
Publish a skill to the npm registry (or private registry).
Pre-publication checklist:
1. Run full skill validation (Level 1 + 2 + 3 from skill-validator.md)
Fail if Level 1 or 2 fails. Warn if Level 3 fails.
2. Verify package.json has `mindforge` field with all required sub-fields
3. Verify CHANGELOG.md has an entry for the current version
4. Check if version already published: `npm info [package-name]@[version]`
If already published: error "Version already exists. Bump the version."
5. Run `npm pack --dry-run` to preview what will be published
6. Confirm with user: "These files will be published: [list]. Proceed? (yes/no)"
7. If --dry-run: stop here, show preview only
8. Publish: `npm publish --access public`
9. Verify: `npm info [package-name]@[version]` — confirm publication succeeded
10. Write AUDIT: `{ "event": "skill_published", "package": "...", "version": "..." }`
11. Report: "✅ [package-name]@[version] published to npm registry"Add an idea to the backlog parking lot (999.x numbering)
Add phase to end of current milestone in roadmap
Generate tests for a completed phase based on UAT criteria and implementation
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Cross-phase audit of all outstanding UAT and verification items
Run all remaining phases autonomously — discuss→plan→execute per phase
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.