Skip to content
Skills Library
Programming · Learning & explanation

cli-reference

/cli-reference

Reference for Nightgauge' own surfaces — the `nightgauge forge` abstraction, the `nightgauge` Go binary subcommands, and the @nightgauge/sdk API — with the gotchas that bite when you use them. Use when authoring or editing a skill, plugin command, automation, or script that shells out to `nightgauge`/`forge` or imports the SDK, or whenever you are about to reach for a bare `gh`/`glab` call and need the forge equivalent.

Repository
nightgauge ↗
Licence
Apache-2.0
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
2
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Reference for Nightgauge' own surfaces — the `nightgauge forge` abstraction, the `nightgauge` Go binary subcommands, and the @nightgauge/sdk API — with the gotchas that bite when you use them. Use when authoring or editing a skill, plugin command, automation, or script that shells out to `nightgauge`/`forge` or imports the SDK, or whenever you are about to reach for a bare `gh`/`glab` call and need the forge equivalent.

Original author description

Reference for Nightgauge' own surfaces — the `nightgauge forge` abstraction, the `nightgauge` Go binary subcommands, and the @nightgauge/sdk API — with the gotchas that bite when you use them. Use when authoring or editing a skill, plugin command, automation, or script that shells out to `nightgauge`/`forge` or imports the SDK, or whenever you are about to reach for a bare `gh`/`glab` call and need the forge equivalent.

How it works

  1. Description
  2. Invocation
  3. When to use
  4. Reference files (read on demand)
  5. How to keep this accurate
  6. Gotchas
  7. Source
Original SKILL.md headings · 83 lines, 501 words
SKILL.md preview
---
name: cli-reference
description: Reference for Nightgauge' own surfaces — the `nightgauge
  forge` abstraction, the `nightgauge` Go binary subcommands, and the
  @nightgauge/sdk API — with the gotchas that bite when you
  use them. Use when authoring or editing a skill, plugin command, automation, or
  script that shells out to `nightgauge`/`forge` or imports the SDK, or
  whenever you are about to reach for a bare `gh`/`glab` call and need the forge
  equivalent.
license: Apache-2.0
metadata:
  author: nightgauge
  version: "1.0.0"
  source: https://github.com/nightgauge/nightgauge
allowed-tools: Read Bash Grep Glob
disable-model-invocation: true
---

# CLI / SDK Reference

> Category-1 (library & API reference) skill for Nightgauge' own surfaces.

<!-- phase-registry: standalone-skill -->

## Description

Nightgauge has three first-party surfaces that skills, plugin commands, and
automations call constantly:

1. **`nightgauge forge …`** — the forge abstraction (issue / pr / project /
   label / repo / auth / graphql / webhook). This is the **mandatory** path for
   every forge operation in a skill — direct `gh`/`glab` is forbidden and
   CI-blocked.
2. **`nightgauge …`** — the deterministic Go binary (board sync, epics,
   gates, health, pipeline history, hooks, …).
3. **`@nightgauge/sdk`** — the TypeScript orchestration
   library the VSCode extension and CI use programmatically.

This skill is a concise index plus a **Gotchas** section. Detailed command tables
and snippets live in the `references/` files — read the one you need on demand.

## Invocation

| Tool        | Command                     |
| ----------- | --------------------------- |
| Claude Code | `/nightgauge-cli-reference` |
| Codex       | `$nightgauge-cli-reference` |
| Others      | Invoke via Agent Skills     |

## When to use

- You are writing/editing a `skills/*/SKILL.md` and need the forge command for an
  issue/PR/project/label operation (never hand-roll `gh`/`glab`).
- You are adding a plugin command or `scripts/` automation that shells out to the
  Go binary and want the right subcommand + flags.
- You are writing code against the SDK (`PipelineOrchestrator`, `ContextManager`,
  `RunStateManager`, events) and need the import surface.
- A `no-direct-gh` lint failure pointed you here.

## Reference files (read on demand)

- **`references/forge.md`** — the `nightgauge forge` surface: every
  subcommand group, the `forge graphql` carve-out for project view/link/list, and
  the GitLab CE/EE caveats.
- **`references/go-binary.md`** — the deterministic Go binary: command groups
  most-used by skills (`project`, `epic`, `issue`, `gate`, `ci`, `health`,
  `pipeline`, `hook`) with examples and the PATH/preflight contract.
- **`references/sdk.md`** — the SDK import surface and CLI entry points.

## How to keep this accurate

These references mirror `--help` output. To check a command is current, run
`nightgauge <group> --help` (or `nightgauge forge <group> --help`) and
reconcile. For the SDK, the source of truth is
`packages/nightgauge-sdk/src/index.ts`. Treat any drift as a bug to fix
here.

## Gotchas

- **Never call `gh`/`glab` directly from a skill.** Use `nightgauge forge …`
  — the `no-direct-gh` lint fails CI on regression, and the abstraction is what
  lets `IB_FORGE=gitlab` work unchanged. (A short allowlist of legacy skills
  exists in `scripts/lint-skills/allowlist.txt`; do not add to it without review.)
- **Project view-create / link / list are a carve-out.** They route through
  `nightgauge forge graphql`, not a dedicated subcommand (ADR-008). The
  GitLab adapter returns `ErrUnsupported` for `forge graphql`.
- **`nightgauge forge project item-remove` is not implemented yet** — don't
  depend on it.
- **Scope a GitHub token per-command in multi-account workspaces** rather than
  switching the global active account (which silently breaks every other open
  workspace). The concrete one-shot-token pattern is in `references/go-binary.md`.
- **The binary is not always on `PATH`.** Resolve it via the Phase-0 PREFLIGHT
  cascade before bare `nightgauge …` calls.

<!-- include: ../_shared/GOTCHAS.md -->

## Source

Part of the [Nightgauge](https://github.com/nightgauge/nightgauge) Issue-to-PR pipeline.
Files in this package (4)
  • SKILL.md 4 KB
  • references/forge.md 3 KB
  • references/go-binary.md 4 KB
  • references/sdk.md 2 KB

Versions

RepositoryScoreLicence
This page · nightgauge/nightgauge100Apache-2.0
Sun-Lab-NBB/ataraxis100Apache-2.0
Sun-Lab-NBB/ataraxis100Apache-2.0
even-realities/everything-evenhub95MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 7d0171d792dc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100nightgauge-cli-reference
    Reference for Nightgauge' own surfaces — the `nightgauge forge` abstraction, the `nightgauge` Go binary subcommands, and the @nightgauge/sdk API — with the gotchas that bite when you use them. Use when authoring or editing a skill, plugin command, automation, or script that…
  • 95nightgauge-docs-write
    Write narrative architecture documentation sections by reading source files and synthesizing accurate, validated content. Use when picking up a documentation issue that requires reading code and writing a structured doc section — without a PLAN.md approval cycle.
  • 100add-command
    Guide for adding new CLI commands or subcommands to todoist-cli. Use when implementing new SDK endpoints, adding subcommands to existing command groups, or extending CLI functionality.
  • 100forge-cli
    Use when an agent needs to call a running three.ws Forge desktop instance from the terminal to generate/export image-to-3D assets through canonical JSON-first automation commands.
  • 100rhdh-forge
    Reads GitHub and GitLab and constructs unexecuted forge payloads for the other RHDH skills: parse an issue, pull request, or merge request reference, fetch issue detail, resolve a plugin workspace, inspect checks or pipelines, read repository files, or build the exact command…
  • 100glab
    Use when creating, reading, updating, or closing GitLab issues and merge requests with the glab CLI.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.