Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

xpepper

@xpepper source repo

11 published skills

  1. ▌
    Code Refactor Review · xpepper bundle
    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".
    0
    installs
  2. ▌
    Plan Feature From Youtrack · xpepper bundle
    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.
    0
    installs
  3. ▌
    Session Wrap Up · xpepper bundle
    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.
    0
    installs
  4. ▌
    Tcr · xpepper
    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.
    0
    installs
  5. ▌
    Tcr Kentbeck · xpepper
    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.
    0
    installs
  6. ▌
    Pr Review Loop · xpepper bundle
    Use when addressing open PR review comments from any reviewer (human or bot). Runs an in-session loop by default; on an explicit `--handoff` request, completes one unit of work per session and stops so the user starts the next. When an external shell loop should drive the sessions instead of the user, use ralph-wiggum-loop.
    0
    installs
  7. ▌
    Pr Review Grill · xpepper bundle
    Use when addressing open pull-request review comments and the user wants to discuss, challenge, and decide each comment one at a time before any code changes. Trigger for requests to grill review feedback, walk through comments individually, debate whether comments are valid, or work through PR feedback collaboratively. Do not use this skill for fast batch triage; use pr-review-loop instead.
    0
    installs
  8. ▌
    Ralph Wiggum Loop · xpepper bundle
    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.
    0
    installs
  9. ▌
    Copilot Review Loop · xpepper bundle
    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; when an external shell loop should drive one session per comment, use ralph-wiggum-loop.
    0
    installs
  10. ▌
    Pr Description Review · xpepper bundle
    Use when reviewing or improving a pull request description so reviewers receive the system context needed for focused, evidence-based feedback. Accepts a GitHub PR URL or number, the PR for the current branch, or pasted description text, and produces a context-gap review plus an improved draft without editing the PR.
    0
    installs
  11. ▌
    Prepare Review Commits · xpepper bundle
    Use when explicitly asked to prepare review-ready commits or make an uncommitted branch review-ready before pushing. Organizes only uncommitted changes into validated, self-contained Conventional Commits; never rewrites history or pushes.
    0
    installs