Menú
Use when connecting apijack to an API — configuring environments, generating the CLI, and switching between configs
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use after a PR has been labeled `first pass reviewed` for at least 4 minutes — verifies CI is still green and no new commits landed since the label, aggregates outstanding non-blocking observations, posts an approval comment, replaces the label with `approved`, merges, and labels every issue referenced by `Closes
Use when the user references a GitHub issue (URL, number, or says "this issue") on the apijack repo and wants to begin work — investigates the issue, resolves ambiguity, then hands off to implementation
Use when origin/dev is ahead of origin/main and the cumulative bump is patch-only — drafts a curated release PR (no Features section), runs scripts/ship.sh, and reports the new release. Refuses to run for minor / major bumps; those still go through ship-release manually.
Use when shipping a release from dev to main on apijack — drafts a curated release-style PR title/description (like v1.7.0), then runs scripts/ship.sh to version-bump, push, merge, and publish
Use after merging an issue PR to dev on apijack — fast-forwards the rolling next branch from dev, waits for the publish-next workflow, and comments the @next install command on the issue
Use when reviewing an open apijack PR that targets the dev branch — verifies acceptance criteria, leaves PR comments on any findings, or merges and hands off to next-deployer
| name | setup-api |
| description | Use when connecting apijack to an API — configuring environments, generating the CLI, and switching between configs |
Connect apijack to any API with an OpenAPI spec to generate a full CLI.
apijack setup # Interactive: URL, credentials, auth detection
apijack generate # Pull spec, generate types/client/commands
apijack --help # See generated commands
apijack setup prompts for:
Credentials are stored in ~/.apijack/config.json for dev URLs. Production URLs require environment variables:
export APIJACK_URL=https://api.example.com
export APIJACK_USER=user@example.com
export APIJACK_PASS=secret
When running as a Claude Code plugin, use the setup MCP tool instead of the interactive CLI:
Use the apijack setup tool to configure environment "dev" at http://localhost:8080
with username admin and password admin123
The MCP setup tool only accepts dev/staging URLs. Production APIs must use env vars.
apijack setup # Add another environment
apijack config list # Show all environments
apijack config switch staging # Switch active environment
apijack generate # Regenerate from new environment's spec
apijack generate creates four files from the OpenAPI spec:
| File | Contents |
|---|---|
types.ts | TypeScript interfaces from component schemas |
client.ts | API client with one method per operationId |
commands.ts | Commander subcommands grouped by tags |
command-map.ts | Lookup table mapping command paths to metadata |
After generating, all API operations are available as CLI commands.
Allow credential storage for internal IPs:
apijack plugin config add-cidr 192.168.1.0/24
apijack plugin config add-cidr 10.0.0.0/8
apijack setup or use the MCP setup toolapijack generate after setupapijack config switch <env> to verify active environment, then apijack generate to refresh