Autonomously audit native local Codex session JSONL for workflow quality, latency, cost shape, tool use, recurring failures, and eval candidates. Use when the user wants scheduled harness observability or evidence-driven harness improvement; do not use for ordinary task execution, application telemetry, or full transcript export.
Verify an existing build artifact itself: metadata, complete download, checksum or size, archive integrity, unpacked contents, and source or lock provenance. Use when artifact contents or completeness must be proven; do not use to trigger builds, releases, deploys, or health checks.
Diagnose the live remote-access layer: SSH resolution, reachability, Tailscale, login-shell PATH, service state, package-manager locks, and remote CLI auth. Use when a named remote host or service is unreachable or unhealthy; do not use for deploy planning or ordinary local repo work.
Establish the current repo, instruction, branch, dirty-worktree, and linked live-object facts before non-trivial work. Use once at the start of repo work when current state or scope is unclear; do not stack it onto every later workflow phase.
Carry already-scoped code changes through verification, commit, push, PR/MR, authorized merge, and authorized cleanup. Use when the requested outcome includes delivery actions; do not use for review-only work, initial repo discovery, CI diagnosis, or deploy execution.
GitLab CLI workflows with `glab` for issues, merge requests, CI/CD, and GitLab API operations. Use when the user needs GitLab command-line automation, issue or MR triage, pipeline checks, API queries, threaded discussion replies, release checks, or work item conversion and hierarchy updates. Prefer `glab api` for reliable scripted flows, while keeping direct CLI commands and local helper scripts available for common MR and pipeline tasks.
Audit and fix repository-level agent scope and permission overreach in prompt or settings files. Use when an agent can execute unrelated commands, escape its stated task, or has contradictory allow/deny rules; do not use for general security review or ordinary application authorization bugs.
Isolate the first actionable failure in an already-red GitHub Actions or GitLab CI run. Use when a concrete PR, MR, workflow, job, or pipeline is failing; do not use for general repo preflight, local test selection, or healthy deploy verification.