api2cli-publish-to-github
Publish to GitHub
Push an api2cli-generated CLI (from ~/.cli/<app>-cli/) to a new GitHub repository.
Phase 1: Pre-flight
Auth
Run gh auth status. If not logged in, tell the user to run gh auth login first. Stop and wait.
Note the GitHub username from the output (e.g. Logged in to github.com account <username>).
Resolve the CLI
If the user didn't specify which CLI, check ~/.cli/ and ask which one. Read package.json to get the package name.
Phase 2: Prepare the repo
From the CLI directory (~/.cli/<app>-cli/):
More from melvynx/api2cli
api2cli
Generate or discover a CLI + AgentSkill for any REST API. Use when: user says 'create a CLI for X', 'wrap this API', 'search if a CLI exists', 'install an existing CLI', 'make a skill for X', 'publish my CLI', 'publish to npm', 'push to github'. Handles registry search, install, discovery, scaffolding, resource implementation, building, linking, skill generation, npm publishing, and GitHub publishing.
104api2cli-publish-to-npm
Publishes an api2cli-generated CLI package to the npm registry. Handles package.json validation, version bumping, building, and npm publish. Use when user asks to "publish to npm", "release to npm", "publish this CLI", "npm publish", "make this installable via npx", "publish a new version", or "update npm".
4