jagreehal-claude-skills

Define the collaboration style between Claude Code and the user for the current session

Review the entire codebase against all jag-reehal-real-claude-skills patterns using the pattern-checker agent. Handles large codebases by chunking files.

Initialize a TypeScript project with jagreehal-claude-skills patterns (tsconfig, eslint, dependencies)

Analyze PR feedback patterns and suggest config updates to catch issues locally

Scaffold a new function following the fn(args, deps) pattern with Result types

Verify code follows jagreehal-claude-skills patterns and report violations

Verify task completion before finishing work. Spawn with task ID, location, and work summary.

Automates real browsers from the command line using a ref-based snapshot-then-interact workflow. Use when you need to drive a live browser, navigating pages, filling and submitting forms, clicking buttons, taking screenshots, scraping or extracting data, testing or logging into web apps, mocking network requests, or verifying responsive layouts. Triggers include "open a website", "fill out this form", "take a screenshot", "scrape this page", "test this web app", "log in to a site", "automate browser actions", or any task requiring programmatic web interaction via the agent-browser CLI.

Detects question-shaped input and forces a literal answer before any action. Use when the user's message contains "?" or trigger patterns like "why did you…?", "will that work?", "have you considered…?", "shouldn't we…?", "doesn't that…?", "is that correct?", especially when the question challenges a decision, requests an assessment, or could be misread as criticism.

Builds production-ready HTTP APIs with thin handlers, consistent error envelopes, health/readiness checks, CORS, idempotency, rate limiting, and graceful shutdown. Use when designing or implementing HTTP endpoints, writing orpc route factories, defining Zod request/response schemas, mapping domain errors to status codes, or adding operational concerns (health checks, X-Request-ID, Retry-After) to a TypeScript API.

Guides completion of development work by verifying tests, presenting structured merge/PR/keep/discard options, and executing the chosen cleanup. Use when implementation is complete and tests pass, when wrapping up a feature branch, or when deciding how to land or discard work.

Traces a code execution path with file:line references and an execution diagram before any change is made, forcing real understanding of fn(args, deps) flows, Result propagation, and workflow composition. Use before fixing a bug, implementing a feature, refactoring, or starting a TDD cycle, whenever you are about to change non-trivial code.

3 hooks across 1 event