pmatos

This skill should be used when the user asks to "autofix pr", "fix pr locally", "fix ci failures", "fix review comments", "iterate on pr", "fix failing checks", "fix pr comments", "make ci green", "fix the build", "address reviewer feedback", or wants to iteratively fix CI failures and review comments on a GitHub PR from the local CLI.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Extract the design system (fonts, logos, colors, CSS tokens, favicons, OG assets) from a public website URL into a fresh local git repo with a fact-only README. Use when the user wants to "extract a design system", "steal a design", "pull fonts and colors from a site", "scrape design tokens", "build a design-system repo from a URL", or prepare assets to upload to claude.ai/design.

This skill should be used when the user asks to "investigate issue", "investigate

Upscale raster images with a local OpenCV EDSR super-resolution model, then produce an exact target pixel size. Use when the user asks to upscale, enlarge, super-resolve, make a higher-resolution version, or create a wallpaper/print-size raster from an existing image while preserving the original artwork.

This skill should be used when the user asks to "plan this", "make a plan", "create an implementation plan", "how should I implement", "design the implementation", "plan the refactor", "plan the migration", "plan the feature", "break this down into steps", "implementation strategy", "deep plan", "thorough plan", or wants a thorough, multi-phase implementation plan with codebase exploration before writing any code.

This skill should be used when the user asks to "get a second opinion", "ask codex", "what does GPT think", "compare with codex", "run codex", "2nd opinion", "second opinion on this code", or wants an independent analysis from OpenAI Codex CLI. Also triggered by the /codex-2nd-opinion command.

This skill should be used when the user asks "is this a skill", "can we extract a skill", "skill extraction", "is there a reusable pattern here", "should this be a skill", "extract skill", or wants to analyze the current session for reusable patterns that could become a Claude Code skill. Also triggered by the /is-skill command.

This skill should be used when the user asks to "profile the codebase", "analyse performance", "find bottlenecks", "benchmark this", "generate a performance report", "measure runtime", "run perf", "check allocations", "why is this slow", or wants a performance investigation of Rust code. Produces a report without modifying code.

This skill should be used when the user asks to "fix performance issues", "optimise the bottlenecks", "implement the performance fixes", "apply the performance report", "speed this up based on the report", or wants to act on a performance report produced by /performance-analyse. Reads a performance report and implements targeted fixes.

Run full verification suite (type-check, lint, test) before marking work done

Show current implementation phase details and verification steps from PLAN.md. Use /phase or /phase <number> to view a specific phase.

Design and write a Symphonika Workflow Contract (WORKFLOW.md or workflow.yml) by grilling the user one question at a time. Use when the user wants to create, edit, or design a Symphonika workflow, mentions "symphonika workflow", asks how to wire up agent states, wait states, merge_pr states, predicates, or transitions, or describes an orchestration pipeline they want to run under Symphonika. Detects unsupported requirements and offers to file a feature request at pmatos/symphonika.

Read and interpret captured Claude Code session events from a project's local sana SQLite database. Use when the user asks to analyze a session, summarize what happened, list tools used, find slow tool calls, review prompts, or otherwise inspect the events recorded by sana hooks. Also use when the user mentions "sana", ".claude/analysis/sessions.db", or session/hook telemetry.

Auto-invoke (1) to convert git commit hashes to WebKit identifiers (NNNNNN@main) and (2) to convert identifiers to commit hashes using git-webkit. Use whenever a commit hash appears in a tool result that will be shared with the user in the WebKit repository.

This skill should be used when the user asks to "search for badminton players", "find a badminton player", "show badminton rankings", "check player ranking", "compare badminton players", "find doubles partners", "show ranking history", "update badminton data", or mentions German U19 badminton, DBV rankings, or badminton player statistics. Enables interaction with the badminton-cli tool for querying German Badminton Association (DBV) U19 rankings.