cli-development
Use when working on the @insforge/cli codebase itself — adding or modifying commands under src/commands/, touching src/lib/api or src/lib/analytics, changing package.json version, wiring telemetry, or preparing an npm release. Covers code conventions, PostHog analytics, agent-skills sync, and the release-triggered publish workflow.
Source facts
- Repository
- InsForge/CLI
- Last source activity
- July 11, 2026 at 20:11
- Detected SKILL.md language
- English
- Stars
- 22
- Forks
- 21
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- cli-development
- description
- Use when working on the @insforge/cli codebase itself — adding or modifying commands under src/commands/, touching src/lib/api or src/lib/analytics, changing package.json version, wiring telemetry, or preparing an npm release. Covers code conventions, PostHog analytics, agent-skills sync, and the release-triggered publish workflow.
- license
- Apache-2.0
- metadata
- {"organization":"InsForge"}
# InsForge CLI Development
See the canonical development guide at [DEVELOPMENT.md](../../../DEVELOPMENT.md)
in the repo root. It covers:
1. **Existing code patterns** — command layout, API clients, config, errors,
output, prompts, ESM imports.
2. **PostHog analytics** — `src/lib/analytics.ts`, event naming, distinct ID,
property allow-list, flushing in `finally`, build-time key injection.
3. **Agent-skills sync** — when to update the `InsForge/agent-skills` repo
alongside CLI command changes.
4. **Release workflow** — version bump → merge → publish a GitHub Release for
`vX.Y.Z` → GitHub Actions publishes to npm.
Always read `DEVELOPMENT.md` before editing files under `src/`, touching
`package.json` version, or shipping a release.
View on GitHub