Development skills

Structured, risk-aware code review of a GitHub pull request using the gh CLI, with diff triage, unresolved-thread suppression, and severity-grouped findings ending in an approve/request-changes verdict.

The English summary is being prepared. Showing the original description.

Address GitHub PR review comments at line, file, and PR level by fetching, evaluating, fixing, committing, and resolving feedback. Use when invoked as `$pr-resolve-review-feedback` or when the user asks to resolve PR feedback.

The English summary is being prepared. Showing the original description.

Rebase the current branch onto a target branch using safety checks and an appropriate rebase strategy. Use when invoked as `$git-rebase` or when the user asks to update/rebase a branch.

The English summary is being prepared. Showing the original description.

Create a git commit following the project's established style

The English summary is being prepared. Showing the original description.

Improve agent harness configuration based on recent friction points. Use when invoked as `$retro` or when the user asks for autonomous cleanup of Codex, agent harness, or migrated Claude configuration.

The English summary is being prepared. Showing the original description.

Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add lifecycle hooks; transform agent configuration, environment, MCP servers, or workspace creation; automate permissions or turn follow-ups; add a screen, sidebar header or footer item, or workspace panel; add Command Center items or slash commands; add composer pills or attachment sources; transform, render, or append agent timeline items; contribute a theme; use Paseo from plugin code; or add plugin RPCs.

The English summary is being prepared. Showing the original description.

Answer questions about the Paseo product and app, including setup, configuration, connectivity, providers, workspaces, updates, logs, and troubleshooting. Use when a user inside Paseo asks how Paseo works, how to configure it, or why something is broken; use the paseo skill instead to operate agents and workspaces through MCP or the CLI.

The English summary is being prepared. Showing the original description.

Explains the ~/.worktrees/<path-key>/<branch> worktree convention, the dotfiles-repo opt-in, and what a dotfiles worktree cannot validate. Use to understand or explain worktree layout and its constraints; use the git-worktree skill to actually create, switch to, or delete one.

The English summary is being prepared. Showing the original description.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

The English summary is being prepared. Showing the original description.

Address GitHub PR review feedback at line, file, and PR level — fetch, evaluate, fix, commit, and resolve. Use when given a PR URL, a review-comment URL, or a PR-level comment URL. Triggers: GitHub discussion URLs, "fix this review comment", "address PR feedback", "resolve PR comments", PR URLs with #discussion_, #issuecomment-, or #pullrequestreview- fragments.

The English summary is being prepared. Showing the original description.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

The English summary is being prepared. Showing the original description.

Create a git commit with Medox conventions (co-author, conventional type/scope). Invoke manually with /commit — do NOT trigger automatically.

The English summary is being prepared. Showing the original description.

Create or update a GitHub pull request following Medox conventions (author spicode-bot, reviewer spideystreet). Invoke manually with /pr — do NOT trigger automatically.

The English summary is being prepared. Showing the original description.

Fetch and display the full status of the current PR — CI checks, GitHub Actions runs, reviews, and code comments — using GitHub MCP tools. Invoke manually with /pr-status.

The English summary is being prepared. Showing the original description.

Use when building a new MCP server in TypeScript, Python, or C# that exposes tools to LLMs.

The English summary is being prepared. Showing the original description.

Use when the user wants to improve architecture, consolidate tightly-coupled modules, or make a codebase more testable.

The English summary is being prepared. Showing the original description.

Use when reviewing code before it merges, whether written by an agent or a human.

The English summary is being prepared. Showing the original description.

Use when the user asks to connect an AI agent to external apps via Composio, or when Composio CLI or MCP setup fails.

The English summary is being prepared. Showing the original description.

Use when planning the migration of a legacy system or monolith — analyzes the source codebase (current repo, or a repo URL cloned to a temp dir) and produces an evidence-based Strangler Fig migration plan with per-domain SPECs. Default target is .NET (Blazor WebAssembly, .NET MAUI, ASP.NET Core); other stacks allowed by user decision. Do NOT use to implement code or when approved SPECs already cover the migration.

The English summary is being prepared. Showing the original description.

Use when generating or editing draw.io/diagrams.net architecture diagrams via MCP or native XML.

The English summary is being prepared. Showing the original description.

Use when the user wants to configure, authenticate, or use Google NotebookLM via the nlm CLI or MCP.

The English summary is being prepared. Showing the original description.

Use when analyzing SonarQube issues and turning them into SPEC SDDs and tracked GitHub Issues for TDD implementation.

The English summary is being prepared. Showing the original description.

Use when turning approved plans, specs, PRDs, or Epics into trackable GitHub Issues.

The English summary is being prepared. Showing the original description.

Build an evidence-backed working model of an existing codebase. Use when you must orient in a large or unfamiliar repository; explain architecture or a subsystem; trace a request, runtime, control, or data flow for a concrete question or bug; analyze a branch, commit, diff, or pull request for behavioral impact and blast radius; or assess AI-generated or changed code against requirements, contracts, invariants, tests, and runtime evidence. Default to read-only investigation. Do not trigger only because a coding task touches an existing repository; use when understanding or verification is the requested outcome or a substantial prerequisite.

The English summary is being prepared. Showing the original description.