ferray

Use when stuck, confused, or disoriented in a crosslink-tracked project — dumps the full context (session state, active issue, locks, blockers, hook config, git state, project rules) so you can re-orient and decide a next action. Trigger when the user says "I'm stuck", "audit", "what's going on", or asks for a context dump.

Use to check on background feature agents launched via /kickoff — running in tmux sessions or docker/podman containers. Reports each agent's state (Working / Idle / Waiting / Done / Error), captures recent output, and offers next-step commands. Trigger when the user says "check on the agent(s)", "how's the kickoff going", or names a `feat-*` / `crosslink-task-*` session.

Use to create a git commit AND auto-document the result on the active crosslink issue. Stages the right files (never `git add -A` blindly), writes a conventional-style message with the issue ref, and adds a `--kind result` comment so the audit trail closes. Trigger whenever the user asks to "commit", "commit changes", "commit and push", or finishes a unit of work in a crosslink-tracked repo.

Use when working in any repo that has `.crosslink/` and the workflow involves issue tracking, sessions, locks, swarms, kickoff, or knowledge pages. Reference for the full crosslink CLI surface plus the harness footguns (auto-CHANGELOG entries on issue close, --no-changelog flag, label-based skip rules, session lifecycle). Trigger when the user mentions crosslink commands, when the crosslink-behavioral-guard hook fires asking for issue creation, or when a session needs to be started/ended/handed off.

Use to author or iterate a feature design document grounded in actual codebase exploration. Drives a four-phase flow (Explore & Interview → Draft → Resolve open questions → Iterate) and writes `.design/<slug>.md` plus a pipeline state file ready for `crosslink kickoff --doc`. Trigger when the user says "design <feature>", "/design …", "iterate the design", or asks to write a design doc / spec / RFC for a feature.

Use to drive a guided release pipeline — version bump, changelog drafting, doc review, test/lint, PR creation, tag, GitHub release, and back-merge. Mixes agent steps (the agent does them) with user-only steps (push / merge / tag, blocked by policy and printed for the user). Trigger when the user says "cut a release", "release v0.6", "/dev-release", or asks to bump version + changelog + tag.

Use to create a `feature/<slug>` branch AND move it into a new git worktree under `<repo-root>/.worktrees/<slug>`, then initialize crosslink hooks and an agent identity in the worktree so a child agent can work there. Trigger when the user says "make a worktree for <feature>", "/featree …", or asks to spin up an isolated branch+worktree for a feature.

Use to create a `feature/<slug>` branch from a human-readable description and register a matching crosslink issue (priority medium, label `feature`). Slugifies the description, validates preconditions (no uncommitted changes, branch doesn't already exist), and checks out the new branch. Trigger when the user says "new feature branch for X", "make a feature branch", or "/feature …".

Use to launch a background Claude agent in tmux (or docker/podman) to implement a feature end-to-end. Delegates worktree creation, prompt building, and session launch to `crosslink kickoff run`, then prints how to attach (`tmux attach -t <session>`) and check status (`/check`). Trigger when the user says "kick off an agent for X", "/kickoff …", or asks for a background agent / sub-agent / worker to do a feature.

Use to run a periodic codebase-health pass — dependency audit, lint, test suite, dead code / TODO scan, doc freshness, crosslink issue hygiene, and build artifacts. Conservative by default (small fixes inline, larger work files a `maintenance`-labelled issue). Trigger when the user says "maintenance", "health check", "audit dependencies", "/maintain", or asks for a periodic project tidy-up.

Use BEFORE implementing code in a crosslink-tracked project — loads `.crosslink/rules/global.md`, the language rules for detected manifests, the project rules, and the active `tracking-<mode>.md`. Replaces the heavy context that would otherwise be re-injected on every prompt. Trigger when the user says "preflight", "load the rules", "ground yourself", or before starting a fresh implementation session.

Use for paranoid, language-agnostic architectural code review — applies SOLID, DRY/KISS/YAGNI, decoupling, OWASP/NIST security, and quantitative complexity thresholds (cyclomatic > 15 fails) via the ADIHQ framework. Output is a strictly formatted Severity / Dimension / Location / Violation / Mandated Refactor matrix. Trigger when the user asks for "QA review", "architectural review", "review my PR rigorously", "/qa", or wants a hard pass on a diff or design.

Use as a pre-commit quality gate — review the working diff for stub patterns (TODO/FIXME/`unimplemented!()`/`todo!()`), debug leftovers (`dbg!`, stray `console.log`/`println!`, commented-out code), then run the project's lint, format, and test suites and verify the active crosslink issue is documented. Prints a PASS/FAIL checklist and hands off to `commit`. Trigger when the user says "review my changes", "/review", "ready to commit?", or asks for a final pass before committing.

Use when applying fixes to Rust code identified by an audit, code review, lint sweep, failing-test triage, or any "fix this list of findings" task. Enforces the discipline of "fix the cause the system architecture calls for, not the symptom" — explicit category choice (root-cause vs. local correctness vs. annotation; defer is forbidden) for each finding, refuses cosmetic conformance and band-aids, forbids unilateral workspace-level changes from a leaf-crate context, and requires honest verification reporting. Pair with `rust-quality` and `rust-gpu-discipline`, which encode the rules being enforced. Trigger when the user says "fix the audit findings", "address the review comments", "fix the clippy errors", "make the failing tests pass", "/fix", or dispatches a subagent to apply fixes from an audit document.

Use this skill aggressively any time the work involves Rust code that touches GPU compute — including ferrotorch (and ferrotorch-* crates), burn, candle, wgpu-rs, cubecl, cudarc, or any project involving CUDA, ROCm, Metal, Vulkan, WGPU, cuBLAS, PTX, WGSL, or kernel dispatch. Trigger on any mention of `.cuda()`, `Device::Cuda(_)`, `.to_device()`, kernel launches, tensor ops, autograd backward passes, JIT codegen, or "GPU acceleration" in a Rust context. Also trigger when the user names a Rust GPU/ML project (ferrotorch, ferray, burn, candle) or asks to implement, port, optimize, or debug compute kernels. This skill exists because the model otherwise systematically defaults to CPU implementations, stubs out GPU code paths, and reports "done" while the work secretly executes on CPU. Use this skill to enforce pre-flight planning, the forbidden-pattern checklist, mechanical verification, and honest reporting so that GPU work actually lands on the GPU.

Use any time you write, review, refactor, or design Rust code (anything in a `Cargo.toml`-bearing crate, `.rs` files, library APIs, async/tokio, error types, traits, unsafe blocks, build scripts). Enforces idiomatic API design (Rust API Guidelines), strict error handling (`Result` + `thiserror`/`anyhow`), clippy lint discipline, safe-`unsafe` with SAFETY comments + miri, structured-concurrency rules for async, and the rustdoc / testing / module-structure baselines that distinguish "compiles" from "shippable." Trigger when the user mentions Rust, asks "is this idiomatic", requests a Rust code review, opens a `.rs` file for editing, or works in a Cargo project. Pair with `rust-gpu-discipline` whenever the work also touches CUDA / wgpu / Metal / cubecl / cudarc / kernels.

Use to walk the user through a guided policy review of the project's crosslink configuration — tracking mode, security policies, language rules, hook implementations, and workflow conventions. Identifies drift from defaults via `crosslink workflow diff` and offers targeted fixes or a `crosslink init --force` reset. Trigger when the user says "review the crosslink config", "audit the workflow policies", "/workflow", or asks whether the hook/rules setup is right.