kunchenguid

Agent-only reference for firstmate harness operations. Use before spawning or recovering a crewmate or secondmate, handling a trust dialog, sending a harness-specific skill invocation, interrupting or exiting an agent, resuming an exited agent, or verifying a…

Load when locating, interpreting, or changing Firstmate home, config, data, state, project, or generated runtime paths.

Load only when auditing or maintaining the complete agent-only skill trigger index.

Agent-only procedure for Firstmate project management. Use before adding, creating, removing, or initializing a project. Cloning or registering a project is add intake and uses the same trigger. Owns project add, create, clone, remove, initialization,…

Generate a "pick up where I left off" fleet digest from firstmate's live fleet state. Use when the captain invokes /bearings or asks for a bearings report, morning brief, status report, catch-up, "where did I leave off", or "what's in the works". Plain…

Load when a scout reports completion, presents a visual artifact for iteration, or is being considered for promotion to implementation.

Enter the away posture when the captain invokes /afk, says they are going afk, `state/.afk-contract` or `state/.afk` exists, an incoming message starts with `FM_INJECT_MARK`, or any `state/.subsuper-*` marker is involved. It writes the durable away-posture…

Agent-only policy for completing investigations and visual reviews without losing unresolved captain calls, and for closing what the captain owns with his actual words. Load before treating an investigation, scout report, structured review, or Lavish review…

Use when changing local branch synchronization, custody recovery, post-review head binding, rebasing or rebase.strategy, private-mirror reconciliation, or force-push safety.

Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach the configured push target. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push…

Use when changing PR body rendering, home-path redaction, artifact path publication, pipeline-attestation markers, or pre-push attestation.

Use when changing test evidence collection, publication, paths, retention, or scratch-directory cleanup.

Use when changing review sessions, finding decisions, the review fix-round carry, review schema retries, agent timeouts, local Test behavior and its live-validation contract, approval overrides and parked gates, or intent conformance.

Use when changing CI readiness, forge check collection, reruns, CI timeouts, CI step findings and fix rounds, or PR lifecycle monitoring.

Use when changing agent model or effort configuration, per-run Pi profile pins, adapter mappings, or eval candidate profiles.

Use when changing fork routing, forge-profile identity, provider-plugin host selection, repository URL persistence, credential redaction, the repo-config trust boundary (trusted-default-branch-only fields), gate-agent instruction neutralization, or…

Use to close contributor PRs that have been waiting on the author for stale-days with no author push, comment, or review. Parameterized owner, disclosure line, and stale days. Firstmate-mark and bot comments do not reset the clock.

Use at Grok Ship intake and whenever work is handed to a crewmate.

Use at the start of every triage wake. Run fetch.py with the charter flags and work only the returned issue and PR numbers, in order.

Use before any final triage decision when the repo has a VISION.md. Read it in full. Per-rule aligns / does not align / cannot tell, with evidence. Claims are not enough. Cannot-tell / inconclusive / undecided is no verdict and blocks auto-merge.

Use when the captain explicitly says ahoy or /ahoy, or asks for a session recap of what happened since they last spoke, plus any visibly unanswered decisions. A standalone captain message whose main ask is "ahoy" is an invocation. History-only. Do not gather…

Use after a ship cloud agent pushes a branch, before any pull request.

Turn complex or visual agent responses into rich, reviewable HTML artifacts the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to grasp…

Use when implementing any feature or bugfix, before writing implementation code

Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a…

Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the…

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root…

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture",…

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff".…

Read or change compact-adviser settings for Codex - the mode (hint or off), the minimum context before a checkpoint is judged, the context budget, TypeSafe request logging, and the TypeSafe API key. Use when the user asks about compaction advice, the /compact…

Use when modifying or testing `packages/codex-plugin` or Codex `/compact` behavior.

Use when changing or evaluating judge prompts, scoring thresholds, usage floors, or judgment eval corpora.

Turn complex or visual agent responses into rich, reviewable HTML artifacts (HTML files) the user can annotate and send feedback on, using the lavish-axi CLI. Use when about to give a plan, comparison, diagram, table, code diff, report, or anything easier to…

Use this skill to generate well-branded interfaces and assets for Lavish, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.

Turn a long-form video transcript into ranked, captioned vertical shorts. Use when proposing soundbite candidates, following the user's target-length setting, deciding whether to override the user's layout/theme/caption defaults, and selecting keywords to…

Use this skill to generate well-branded interfaces and assets for Short Pipe, either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.

Use when the user asks to run GNHF, says they are going to sleep or leaving and wants an agent-managed coding run, asks to supervise, steer, or review an active GNHF run, or gives feedback on GNHF results.

Agent eXperience Interface (AXI) — ergonomic standards for building CLI tools that agents use via shell execution. Use when building, modifying, or reviewing any agent-facing CLI.

Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web…

Summon Kun to solve your problems. Use on /kun or when asked how Kun thinks, builds, or solves problems.

Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved. Use on /vision or when asked to create or refine a project vision.