claude-config

Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.

Autonomous PR review agent that monitors Greptile, fixes issues, and merges when approved. Runs in background after PR creation. Loops until 5/5 confidence score then auto-merges. Use after creating a PR for fully hands-off review workflow.

CDP-based browser automation via browser-tools CLI

Call MCP server tools as CLI commands via mcporter

Semantic search for code and web. Use mgrep for natural-language/intent queries and web search. Use built-in Grep for exact strings/regex. Use Glob for file names.

Manages the OpenClaw trading system on openroach.exe.xyz. SSH admin operations for Kalshi proxy, credentials, kill switch, logs, and trade queries. Triggers include "openclaw", "check trades", "kill switch", "trading logs", "restart proxy", or /openclaw.

Persistent tmux sessions for background monitoring and long-running processes

Complete catalog of all available tools, skills, hooks, and agents

Add comprehensive documentation to source code files across multiple languages. Automatically detects file language and applies appropriate documentation standards (Python docstrings, JSDoc, JavaDoc, Go doc comments, Rust doc comments, etc.). This skill should be used when documenting code, adding missing documentation to functions/classes/modules, or improving documentation standards across a codebase. Trigger phrases include "add documentation", "document this code", "add docstrings", "add JSDoc".

Performs thorough, autonomous codebase analysis using layered deep-dive methodology. Produces comprehensive markdown report. Use when joining a project, before architectural changes, for health checks, or onboarding. Triggers include "analyze this codebase", "understand this project", "codebase overview", "what does this code do", or /analyzing-codebases. Supports --quick, --thorough, --exhaustive modes.

This skill should be used when working with the Atomism framework for schema-first agent orchestration. Use for creating, registering, and running atoms, managing capabilities, executing workflows, and extracting atoms from existing code or skills.

Generate API documentation from Python docstrings using pdoc, sphinx, or mkdocs. This skill should be used when the user wants to create browsable HTML API documentation from existing Python code, generate reference docs for a package, or set up automated documentation for a project. Trigger phrases include "generate API docs", "create documentation", "build docs from docstrings".

Jiro's Phase 0: Automated mechanical verification. Runs linters, typecheckers, and static analysis before human review. Catches issues that should never require human attention. Must complete before any code review.

Comprehensive Python code review checklist for Jiro. Obsessive, methodical verification of every Python-specific concern. Use as part of Jiro's multi-pass review methodology.

Journals architecture decisions, patterns, mistakes, and codebase state. Maintains institutional memory at .claude/journal.md. Use when starting in a new repo, after significant decisions, or when establishing patterns. Triggers include "update the journal", "document this decision", "journal this pattern", "what did we decide", or /journaling-codebase-decisions.

Exhaustive multi-agent codebase review that writes all reports to docs/reviews/YYYY-MM-DD/. Each agent writes its own report to disk before returning, so reports survive context window limits. Use when you want a thorough review of src/ or any directory. Triggers include "review to disk", "exhaustive review", "full codebase review", or /review-to-disk.

Scrapes websites and extracts content using Firecrawl API. Single-page scraping, full site crawling, URL mapping, and structured data extraction. Handles JavaScript-rendered content. Triggers include "scrape this URL", "crawl the documentation", "get all links from", "extract data from website", "map this site", or /scraping-websites.

Wrap up the current session by reflecting on what was learned and identifying skills, rules, or hooks that should be created or updated. Use at end of session, before switching contexts, or when Q says "wrap up", "let's stop", or /wrap.