Jarvis-Code

Use when working with git operations including commits, branches, worktrees, and PRs. Covers the full git workflow from feature isolation to PR submission.

Complete PR submission pipeline with local sub-agent review before pushing, CI verification, and automated review integration. Always dispatches code-reviewer and code-simplifier for code changes, plus conditional reviewers (security, performance, dependency, accessibility, i18n, type-design, etc.) based on change type. Waits for CI with `gh pr checks --watch`. Integrates CodeRabbit and Greptile feedback.

GitHub CLI patterns for PR reviews, comments, and API operations. Use when working with gh api commands, especially for review threads and comments.

Use when following a written plan or task list. Checkpoint verification at each step. Triggers - execute plan, follow plan, implement plan, next step, continue, proceed.

Use for parallel branch development with workspace isolation.

Use when implementing analytics, event tracking, or setting up dashboards. Covers privacy-first tracking, event patterns, and common analytics tools.

REST/GraphQL API design patterns, error handling, and versioning. Use when designing APIs, handling errors, or making API architecture decisions.

Efficient handling of long-running commands. Use when running tests, builds, or any command that takes more than a few seconds. Prevents token waste from polling.

Use when generating ideas, exploring options, defining requirements, or making decisions. Covers both discovery (what to build) and approach (how to build). Triggers - ideate, brainstorm, options, alternatives, explore, what if, could we, ways to, approaches, spec, requirements, user story.

Use when debugging frontend issues in the browser. Covers DevTools usage, network debugging, performance profiling, and console patterns.

Use when sharing development progress publicly. Covers progress sharing, changelog writing, social media updates, community engagement, and milestone announcements.

Use when reviewing code changes or conducting PR reviews.

Use when working with CodeRabbit AI code review. Covers triggering reviews, interpreting feedback, addressing comments, and PR workflow integration.

Use when making commits. Conventional commits, atomic changes.

Use when implementing web scraping, data extraction, or automated browser interactions. Covers Puppeteer, Playwright, rate limiting, and ethical scraping.

Schema design, migrations, queries, and indexing strategies. Use when designing database schemas, writing migrations, or optimizing queries.

Use when encountering bugs, test failures, or unexpected behavior. Hypothesis-driven debugging.

Use when multiple independent tasks can run simultaneously. Maximizes throughput through parallel Task tool invocations.

Meta-skill for rapidly learning new domains. Covers domain research process, expert consultation simulation, knowledge validation, and documentation generation.

Use when designing UI components, implementing accessibility, responsive layouts, or integrating with design systems.

Use when rapidly prototyping ideas into products. Covers MVP scoping, feature prioritization, tech stack selection, timeline estimation, and launch checklist.

Use when identifying opportunities to improve the Jarvis system, adding patterns, creating skills, or updating rules based on repeated guidance.

Use when working with infrastructure, deployments, Docker, CI/CD, or server management. Covers containerization, deployment workflows, and DevOps patterns.

Review and clean up the Linear backlog. Close stale issues, update priorities, merge duplicates, request clarification. Triggers - backlog grooming, backlog cleanup, groom backlog.

Fix Linear issues tagged with "bug". Either produces a PR with the fix or explains why it won't be fixed. Triggers - fix bugs, linear bugs, bug triage, resolve bugs.

Plan issues for an upcoming Linear cycle/sprint. Review backlog, prioritize, assign to cycle, balance workload. Triggers - cycle planning, sprint planning, plan cycle.

Create a Linear Document with technical design using Approach Mode brainstorming. Same process as /brainstorm how, outputs to Linear Document. Triggers - linear design, design to linear, technical design, architecture decision.

Review Linear issues tagged with "feature-request". Decide to spec, add to roadmap, merge, or reject. Triggers - review feature request, user request, customer feedback.

Intelligent work tracking. Automatically classifies issues, gathers codebase context, and creates well-formed Linear tickets. Triggers - linear, issue, track, bug, todo, fix, question, debt.

Create Linear Issues from requirements using the plan process. Same process as /plan but outputs to Linear Issues instead of file. Triggers - linear plan, plan to linear, create issues from plan.

Generate health report for a Linear project. Progress vs plan, blocked issues, overdue items, risk assessment. Triggers - project health, project status, project report.

Answer Linear issues tagged with "question". Explores codebase and produces decisions - never code changes or PRs. Triggers - answer questions, linear questions, question triage.

Refine Linear tickets tagged "refine" or in triage. Pull GitHub context, clarify scope, add acceptance criteria, improve descriptions. Triggers - refine ticket, ticket refinement, triage, improve ticket.

Create a Linear Project from requirements using Discovery Mode brainstorming. Same process as /spec but outputs to Linear instead of file. Triggers - linear spec, spec to linear, create project from spec, linear project.

Resolve Linear issues tagged with "tech-debt". Decide to address now, schedule, or close. Triggers - resolve tech debt, technical debt, debt triage, cleanup.

Use when working with MCP servers for enhanced capabilities like documentation retrieval, database access, or specialized tools. Triggers - mcp, context7, documentation lookup, external docs.

Next.js App Router patterns, server actions, caching, and routing. Use when working with Next.js 14+ features.

Use when implementing payment flows with Stripe or Polar. Covers checkout integration, webhooks, subscriptions, and error handling.

Use when you have a spec or requirements for a multi-step task, before touching code. Triggers - plan, design, architect, implementation plan, spec, requirements.

Process PR review feedback, categorize comments, create tracking issues for deferred items, and resolve conversations. Can be invoked standalone or during submit-pr Phase 6.