vivswan-skills

Use when writing code changes, sweeping or shortening comments (including file-size or comment-cap findings), or asked to apply house code standards.

Use when Codex on macOS must drive the user's Chromium browser (Brave, Vivaldi, Opera, Edge, Chrome) through the bundled Chrome plugin, or that plugin fails with "Codex auth token is unavailable", a missing extension connection, or a stale plugin cache after a desktop app update. Codex only.

Use when creating a skill or memory, when one fails in practice, or when the user reports one misbehaving or stale.

Use when writing or reviewing a page of a repository's documentation (a README, a guide, a reference or architecture page, a docs site), or when a change moves code across the layers an architecture page declares.

Use when asked to humanize text, remove AI tells, check whether text reads as AI-generated, or draft prose that must not sound AI-written.

Use when you just corrected an agent or fixed the same failure class twice, or when a change removes a rule, guard, or check.

Use when code or a design guards invariants with repeated runtime checks, lifecycle flags, or the same guard at every consumer, or when asked to make invalid states unrepresentable or parse-don't-validate.

Use when asked to act as orchestrator, orchestrate with worktrees, run a fleet of parallel subagents on multi-track work, or build and manage many PRs in parallel.

Use when opening a pull request, writing or changing its body or title, writing an issue, or replying to an issue reporter or outside contributor.

Use when a review round lands on an open PR, when flipping its draft state, deciding who merges, or landing a change by PR merge or direct push.

Use when asked to rubber duck a change, get a second opinion, or run an independent cross-model review of code changes.

Use when about to report a zero or absent reading, an alarming finding, a success claim, or stillness from a probe or status read, so the reading is evidence-bearing and controlled first.

Use when pushing commits to a remote with CI, merging a PR, or when asked whether a pipeline passed, so every push and merge gets a background watcher.

Use when creating, removing, or handing over git worktrees, retiring a branch after it landed, or when several actors share one repository through worktrees.