Ven0m0

Collect, deduplicate, enrich, triage, and convert code comments (TODO/FIXME/HACK/NOTE/OPTIMIZE/SECURITY/DEBT) into structured, dependency-ordered task lists ready for autonomous agents. Use when processing technical debt, converting code notes into tracked work, preparing task backlogs, or generating executable task graphs. Triggers: TODO triage, fixme list, tech debt scan, task extraction, comment analysis.

Scaffold repo-local Ralph autonomous harness under scripts/ralph/. Use when user runs /flow-next:ralph-init.

Use when user wants to Find and remove genuine dead code using deadcode + vulture. Filters known false positives (dataclass fields, protocol methods, dunder hooks). Run before a cleanup commit.

Use when user wants to Scan the repo for TODO code comments, TODO-titled GitHub issues, and predict the next best work item to tackle. Reusable across any git repository.

Packages repositories into AI-friendly bundles with Repomix and can reconstruct files from existing Repomix outputs. Use when packaging codebases for LLM analysis, creating repository snapshots, reversing bundles, or preparing security audits. Triggers include "repomix", "package codebase", "repomix-unmix", "extract-bundle", "AI-friendly", or "LLM context".

Analyzes bash scripts for performance bottlenecks, coding standards, and modern tool replacements. Use when optimizing shell scripts, consolidating scripts, or preparing for production. Triggers include "optimize bash", "shellcheck", "script performance", or "consolidate scripts".

Use Cloudflare Browser Rendering REST APIs to extract rendered webpage content as Markdown or crawl whole sites asynchronously. Use when normal web_fetch is insufficient because pages are JavaScript-heavy, require render-time extraction, or you need multi-page site crawling for docs, research, monitoring, or RAG preparation. Prefer this skill for: (1) converting a rendered page to Markdown with /markdown, (2) crawling a documentation site or knowledge base with /crawl, (3) controlling render/load behavior via gotoOptions, cookies, auth, userAgent, or request filtering. Do not use it for interactive login/button-click workflows; use browser for those.

Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.

Use when user wants to Run the Arc Raiders AutoScrapper validation stack after edits. Use for linting, typing, tests, workflow checks, and broader repo validation.

Use when user wants to Update Metaforge snapshots and bundled default rules

Use when user wants to Validate OCR changes against failure corpus before shipping

Add a new OCR regression fixture from an ocr_debug image. Use when a scan misidentified an item and you want to lock in the correct result as a test case.

Use when user wants to Run full validation, push branch, and open a PR with appropriate context notes

Workflow for safely adding, removing, or renaming persisted config fields in config.py. Use whenever editing dataclass fields in src/autoscrapper/config.py. Covers incrementing CONFIG_VERSION, writing a migration function, and validating the round-trip.

Use when user wants to Find and remove genuine dead code using deadcode + vulture. Filters known false positives (dataclass fields, protocol methods, dunder hooks). Run before a cleanup commit.

Use when user wants to Replay OCR corpus against a candidate threshold value to validate before shipping a threshold change. Use specifically for changes to fuzzy match threshold or score_cutoff. For general OCR code changes, use /ocr-corpus-replay instead.

Automatic quality control, linting, and static analysis procedures. Use when validating code changes for syntax correctness and project standards. Triggers on keywords: lint, format, check, validate, types, static analysis.

Refactoring and cleanup - improving code structure, removing dead code, eliminating duplication, or pre-merge cleanup. Use when code is hard to maintain, has dead code or debug artifacts, or needs pre-merge polishing.

Fix a GitHub issue end-to-end - from reading the issue, understanding requirements, implementing the fix, writing tests, and creating a commit. Use when given a GitHub issue number or URL to resolve.

Optimize code for readability, performance, maintainability, and security across Bash, Python, and Rust. Use when asked to improve code quality, optimize performance, add type safety, or refactor for idioms.

Create, debug, and optimize GitHub Actions workflows with security best practices. Use when asked to "create workflow", "fix workflow", "add CI", or needs help with GitHub Actions.

Review code changes (diffs, PRs, patches) and provide structured, actionable feedback on correctness, maintainability, and test coverage. Use when the user asks for a code review, requests feedback on a patch/PR, or wants an assessment of changes.

Craft immersive, high-performance premium web experiences with advanced motion, typography, and architectural craftsmanship. Use when building award-level landing pages, interactive portfolios, or components requiring top-tier visual polish.

Coordinates greenfield app scaffolding and rapid prototyping with official starters and focused sub-agents. Use when creating a new application or shaping a fast prototype.

Use when user wants to Coding patterns and conventions extracted from the Win dotfiles repository. Covers commit style, PowerShell script structure, file organization, CI behavior, and issue tracking. Load when writing scripts, commits, or docs for this repo.

Use when the user wants to commit local changes, sync with GitHub, and push. Triggers on "merge my changes", "push to remote", "commit and push", "merge into main", "sync local changes", "get my changes onto main", or any request to integrate local/branch work into main and push to GitHub.

Platform-neutral guidance for using Open Computer Use, the open-source Computer Use MCP server and CLI for macOS, Linux, and Windows. Use when an agent needs to install, verify, troubleshoot, configure, or operate Open Computer Use through its native CLI, stdio MCP server, or direct Computer Use tool calls.

Orchestrates repository and file system cleanup through sequential phases: separating code from docs, organizing folder structure (both repos and general directories), removing legacy code, removing script clutter, pruning documentation sprawl, cleaning documentation content (emojis, hyperbole, 'comprehensive'), and eliminating duplicate files. Use when cleaning repositories, organizing projects, removing legacy code, pruning AI-generated docs, organizing Downloads/Documents/project folders, finding duplicates, restructuring folder hierarchies, or establishing organizational systems. Triggers on: 'clean up repo', 'janitor', 'organize', 'repository cleanup', 'remove legacy', 'prune docs', 'find duplicates', 'organize folder', 'project structure', 'tidy workspace', 'folder cleanup', 'downloads organization'.

Use whenever the user wants Claude to connect to, inspect, run commands on, or move files to/from a device on the local network via SSH - a Raspberry Pi, home server, NAS, router, or any other LAN box, whether referenced by a ~/.ssh/config alias, a raw IP (e.g. 192.168.1.x), or a hostname like "the pi" / "my nas" / "the server in the closet". Also use for discovering what's alive on the LAN, setting up key-based auth to a new device, or running the same check across several LAN hosts. Trigger even if the user doesn't say "SSH" explicitly - e.g. "restart the service on the pi", "grab the logs off my nas", "what's running on 192.168.1.50", "copy this file to my server".

Transforms complex projects into clear, actionable plans through design exploration and strategic breakdown. Guides design validation before implementation, decomposes features into atomic tasks, maps dependencies and critical paths, assesses risks, estimates effort and timeline. Use for new features, refactoring, migrations, team scaling, complex debugging. Provides both design options and implementation roadmaps.

Use when user wants to Scan the repo for TODO code comments, TODO-titled GitHub issues, and predict the next best work item to tackle. Reusable across any git repository.

Create a GitHub pull request following project conventions. Use when the user asks to create a PR, submit changes for review, or open a pull request. Handles commit analysis, branch management, PR template usage, and PR creation using the gh CLI tool.

Run steelseriesgg-rs's benchmark binaries before and after a change and report the timing delta.

Run the full local CI matrix for steelseriesgg-rs, matching .github/workflows/ci.yml exactly. Use this whenever the user asks to run CI, check all feature variants, run the full test suite, verify before pushing, or run clippy/fmt/tests across features. Invoke proactively before any push or PR review.

Run the protocol fuzzer (`ssgg fuzz`) against a connected keyboard with safety guardrails, capture responses, and fold results back into docs/development/ notes.

Rust conventions for steelseriesgg-rs — error handling, unsafe, feature-gated commands. Use when writing or refactoring any .rs file or Cargo.toml.

Use when user wants to Find and remove genuine dead code using deadcode + vulture. Filters known false positives (dataclass fields, protocol methods, dunder hooks). Run before a cleanup commit.

HID protocol constraints for steelseriesgg-rs device code. Automatically load when editing any file under src/devices/. Contains hard rules about HidReportBuilder usage, unsafe block documentation, and experimental command code labeling.

Run the correct validation checks for changed files in this repository (Bun frontend checks, uv Python checks, and workflow or guidance verification).

Bootstrap Copilot guidance for any repository by creating or updating `.github/workflows/copilot-setup-steps.yml`, focused lint/check/test workflows, `.github/instructions/*.instructions.md`, and `.github/skills/*/SKILL.md`. Use when asked to initialize Copilot guidance, scaffold repo instructions or skills, create or update `copilot-setup-steps`, or add Copilot-facing validation workflows.

A comprehensive guide for GitHub Copilot to craft immersive, high-performance web experiences with advanced motion, typography, and architectural craftsmanship.

Build Model Context Protocol (MCP) servers with tools, resources, and prompts. Use when creating MCP servers, choosing stdio vs HTTP transport, debugging MCP behavior, or implementing MCP patterns in Python or TypeScript.

Optimize code for readability, performance, maintainability, and security across Bash, Python, and Rust. Use when asked to improve code quality, optimize performance, add type safety, or refactor for idioms.

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

Bootstrap Copilot guidance for any repository by creating or updating `.github/workflows/copilot-setup-steps.yml`, `.github/instructions/*.instructions.md`, and `.github/skills/*/SKILL.md`. Use when asked to initialize Copilot guidance, scaffold repo instructions or skills, or create or update `copilot-setup-steps`.

Expert knowledge of bash scripting standards for this dotfiles repo. Covers mandatory header, safety flags, variable quoting, banned patterns, and modern tool idioms (rg/fd/bat/eza/jaq). Use when writing or reviewing any .sh file in Home/.local/bin/ or shell config files.

Expert knowledge of YADM + Tuckr deployment model for this repo. Covers Home/ vs etc/ path conventions, yadm-sync workflow, and system config deployment. Use when working with dotfile deployment, sync operations, or adding new config files.

Multi-shell awareness for this repo's Bash/Zsh/Fish configs. Covers Zimfw (Zsh), ble.sh (Bash readline), Fish functions, and Starship prompt. Use when editing shell init files, adding aliases, or working with shell-specific syntax.

jq JSON processing: query, filter, transform JSON. Use when parsing JSON files, filtering arrays/objects, transforming structures, or extracting fields from JSON.

Validates JSON data against JSON Schema using the z-schema library. Use when the user needs to validate JSON, check data against a schema, handle validation errors, use custom format validators, work with JSON Schema drafts 04 through 2020-12, set up z-schema in a project, compile schemas with cross-references, resolve remote $ref, configure validation options, or inspect error details. Covers sync/async modes, safe error handling, schema pre-compilation, remote references, TypeScript types, and browser/UMD usage.

Use when editing or reviewing MC-Server shell tooling in `tools/` and related shell helpers.

Use when validating changed files in this repository with the narrowest relevant checks (ruff, biome, shellcheck, claudelint, pytest).

Arch Linux / CachyOS script conventions for this repo — AUR helper fallback chain, package operations, systemd interaction, mirror ranking, and Rust build flags. Use when editing Cachyos/ scripts.

Linux-OS repository bash coding standards — forbidden patterns, required idioms, performance rules, and the canonical script template. Use when writing or reviewing any .sh file in this repo.

Raspberry Pi / Debian script conventions for this repo — APT fallback chain, F2FS imaging, loop device management, chroot operations, and ARM detection. Use when editing RaspberryPi/ scripts.

Use when the user wants to commit staged/local changes, sync with the remote (and an upstream fork source if one is configured), and push — without losing local work. Triggers on "merge my changes", "push to remote", "commit and push", "merge into main", "sync local changes", "get my changes onto main", "sync with upstream", "pull upstream changes", "pull remote changes while keeping mine", or any request to integrate local/staged/branch work with a moved-on remote and push it. Detects the repo's actual remote topology instead of assuming one — works the same way in any git project.

Run this repo's (dotfiles-pi) Bash validation recipe from AGENTS.md — bash -n, shellcheck, and a bash-language-server parse check — against one script, a list of scripts, or every tracked *.sh file. Use when asked to "validate", "check", or "lint" scripts in this repo, before claiming a script change is done, or before a commit that touches .sh files. A PostToolUse hook already runs this per-edit; use this skill for a full/batch pass instead.

Validate dietpi.txt and dietpi-wifi.txt in this repo (dotfiles-pi) against the build-image.yml CI gate, this repo's secret-handling rules, and DietPi's real software-ID catalog. Use before committing changes to dietpi.txt/dietpi-wifi.txt, before triggering an image build, or whenever asked to check/validate/review DietPi config in this repo.

Initialize or refresh Copilot guidance for this Windows automation repo. Use when updating bootstrap files, repo-specific instructions, and reusable skills.

Run the narrowest repo-specific validation for AutoHotkey, PowerShell, CMD, workflows, and agent guidance changes. Use when checking changes before reporting completion.

Scaffold a new userscript in userscripts/src/ with the correct header, guard pattern, and project conventions for this repo.