glab — GitLab CLI

Use glab to operate GitLab from the terminal. All commands assume glab is authenticated; verify with glab auth status before making changes.

Critical Rules for Agents

1. Confirm repository context before mutating. Use glab repo view -F json or pass -R GROUP/PROJECT when there is any ambiguity.
2. Never use interactive mode. Always pass --yes/-y to skip prompts and --no-editor where available.
3. Prefer JSON output. Use -F json or --output json for parseable data. Fall back to text only for human display.
4. Repo context. When inside a git repo linked to GitLab, glab auto-detects the project. Use -R OWNER/REPO or -R GROUP/NAMESPACE/REPO to target a different project.
5. Never expose tokens. Do not log, print, or embed tokens in commands. Use glab auth status to check auth, never glab config get token.
6. Avoid TUI/browser commands. glab ci view launches a TUI and --web opens a browser. Use JSON/list/view commands instead.
7. Never invent flags. If the skill or reference file doesn't show a flag, verify with --help before using it.
8. Never pass multi-line strings inline. Write markdown or JSON content to /tmp/file.md first, then reference it.

Agent Safety — Verified Flags

These flags are confirmed via --help. Do not assume other flags exist.