xpepper

Use when addressing open PR review comments from any reviewer (human or bot) within the current agent session. For a fresh-context-per-comment approach, use ralph-wiggum-loop instead.

Use when you want GitHub Copilot to review a PR and automatically address its feedback within the current agent session. For any reviewer (human or bot), use pr-review-loop; for a fresh-context-per-comment approach, use ralph-wiggum-loop.

Use when context window exhaustion is a concern or when addressing a large volume of PR comments — spawns a fresh agent session per comment via an external shell loop. For an in-session approach, use pr-review-loop or copilot-review-loop instead.

Enforces Test && Commit || Revert (TCR): run tests after each micro-change, commit only on green, discard the change on red. ALWAYS trigger when the user mentions TCR, test-commit-revert, or wants strict incremental commits with no red states kept in the working tree or history. The agent makes tiny changes, runs the full test suite, and either commits on green or reverts everything on red — never accumulating broken code. Do NOT trigger for general TDD questions, test framework setup, CI pipelines, or code coverage — those do not need this skill.

Guide users through TCR (Test && Commit || Revert), TCRDD, and git-gamble workflows. ALWAYS trigger when a user mentions TCR, TCRDD, "test commit revert", "git gamble", or "git-gamble". Trigger when a user wants to combine TDD with automatic commits/reverts, enforce baby steps via a commit-or-revert loop, or asks about the --red/--green/--refactor flags. Trigger when someone says they want to "develop with TDD and TCR", "use TCR to force smallest steps", or "gamble" on their tests. Do NOT trigger for general TDD-only questions, general unit testing questions, test framework setup, CI pipelines, mocking, or code coverage — those do not need this skill.

Leverage Perplexity CLI for web research, deep reasoning, and independent validation. Use when you need current/external knowledge, want a second opinion before decisions, or want to delegate complex analytical thinking to specialized reasoning models. Complements (not replaces) standard web tools. Can be invoked directly or spawned as a subagent.

Closes out a coding session: reviews git changes, updates agent instructions and project docs, captures gotchas, decisions, and follow-up tasks. Trigger phrases: wrap up, hand off, save what was learned, update AGENTS.md/CLAUDE.md, capture lessons, record mistakes, note next steps, what should we commit.

Generate a spec and implementation plan from a YouTrack issue, grounded in your codebase. Use when a YouTrack issue ID (e.g. INTOP-1486, ABC-123) appears in a message AND the user wants a spec, plan, or implementation breakdown. Triggers on: 'create a spec from INTOP-1486', 'plan ABC-123', 'DEV-4421 — give me a plan'. Does NOT trigger for: status checks, adding comments, PR reviews, debugging, or writing tests.

Use when starting work on a branch and needing full context before answering questions, reviewing code, or implementing changes. Analyzes the diff from the base branch, commit history, and linked PR (title, body, review comments) to build a complete picture of what the branch does and why.

Use when reviewing code changes, PRs, or diffs for quality issues such as duplicated logic, inconsistent naming, unnecessary abstractions, slop, or poor composition. Triggers when asked to review, check, or clean up code changes — including "review this", "check this diff", "is this clean", or "does this fit the codebase".

This skill should be used proactively—without waiting for the user to ask—whenever Claude notices a refactoring opportunity, code smell, or improvement while working on any task. Trigger on observations like "this function is getting long", "this logic appears to be duplicated elsewhere", "this variable name doesn't reveal its intent", "there's no test for this module", or "this abstraction is doing too much". The skill records the opportunity silently without interrupting the current task, so Claude can stay focused while nothing goes unnoticed.

This skill should be used when the user asks to "practice TDD", "start a kata", "code kata", "test-driven development", "red green refactor", mentions "object calisthenics" constraints, or when agents in the tdd-kata plugin need TDD cycle guidance. Provides comprehensive TDD best practices and kata workflow orchestration.