PaulRBerg

Commit staged or intended changes: compose a Conventional Prefix or Natural Language message, then use ai-commit — with --all, --staged, --close, --finding, or --push. Also squash a branch into one commit with --squash.

Use for targeted EVM chain, account, transaction, RPC, explorer, bridge, and DEX evidence: chain name/ID, native symbol, RouteMesh, wallet balances and DeFi positions via DeBank/Blockscan in Chromium, cross-chain USD portfolio value or net worth, token/NFT…

Audit an entire repository with fresh eyes for correctness errors, bugs, omissions, duplication, inconsistencies, stale, duplicate, or tautological tests, stale comments, and other mistakes supported by evidence. Fix every safe issue and verify the result.

Refactor naming and repository structure exhaustively while preserving behavior and external contracts.

Use for dependency updates: bump npm/pnpm/yarn/bun packages, check outdated, or run taze.

Use when CSV, TSV, or Excel (.xlsx) is the primary input/output: design or review text-table schemas, inspect, transform, validate, convert, or recalc formulas, or create/fix spreadsheets. Do not trigger when tabular data is incidental.

Use for GitHub PR/issue/discussion workflows: create/update PRs, issues, or discussions and post issue or discussion comments; triggers include yeet.

Use for CoinGecko/cg CLI crypto market data: prices, market cap, trending coins, top gainers/losers, coin search, or historical/OHLC data.

Create or polish repo agent context: README.md, AGENTS.md/CLAUDE.md, project-installed and source-catalog skills, and other Markdown context docs.

Audit an entire repository with fresh eyes for correctness errors, bugs, omissions, duplication, inconsistencies, and other evidenced mistakes; fix every safe issue and verify the result.

Audit multiple interdependent repositories for alignment, then plan and apply surgical fixes for drift and duplication.

Wind down a long-running session fast when the user must leave — freeze new work, preserve active subagents, secure finished work, and hand off the remainder via task-handoff.

Use for GitHub PR/issue/discussion workflows: create/update PRs, issues, or discussions and post issue or discussion comments; triggers include yeet.

Use Chrome DevTools through PRB's shared attach-only Chromium browser for browsing, debugging, automation, visual inspection, console or network analysis, performance or memory profiling, screencasts, and Wayback Machine research.

Use to find, compare, and recommend current tools, packages, libraries, CLIs, VSCode extensions, agent skills, databases, or infrastructure options for a development task.

Use for current official documentation about Codex, Codex CLI, or Claude Code behavior, configuration, prompting, skills, permissions, tools, surfaces, capabilities, troubleshooting, hooks, app-server, or hook trust; consult the relevant official source…

Audit macOS efficiency, background load, cache sprawl, Homebrew cleanup, login items, LaunchAgents, and safe developer cache cleanup. Use for Mac performance, disk cleanup, cache cleanup, background process, launch daemon, or login item audits.

Capture global dotfile changes made by a CLI installer into the chezmoi source, then commit. Use after an installer (curl pipe to sh, npm -g, brew, etc.) edits shell rc files or PATH. Pass the install command as the argument. The skill runs it and diffs what…

Add a new dependency to the macOS tool installation manifest

Add custom zsh completions for a tool.

Write and debug Foundry tests and Solidity scripts. Use when writing unit, fuzz, fork, or invariant tests, writing bulloak BTT .tree specs (Branching Tree Technique), using cheatcodes, benchmarking gas, measuring coverage, writing deploy scripts, or working…

Write and modify production Solidity contracts in Foundry projects. Use when writing a contract, implementing a function, adding errors, events, or structs, designing contract architecture, optimizing gas, hardening security, planning upgrades, or working in…

This skill should be used when the user asks to "bump version", "release a new version", "bump the version", "prepare a release", "update version numbers", "what version should this be", or mentions version bumping, semver analysis, or release preparation.

This skill should be used when the user asks to "release and bump", "publish and bump", "release to npm and update new-ui", "release and update consumer", "publish and migrate", or mentions releasing a @prb/effect-* package and bumping it in new-ui.

Use when adding a new EVM chain to @prb/crypto-registry and propagating it to the evm-atlas skill in ~/projects/agent-skills. This includes Chainlist/Chrome DevTools research, wrapped-native enrichment, verification, commits, and surgical skill publication.