agent-skills

Turns one or more raw items (bugs, feature ideas, TODOs, call notes, bullet lists) into well-structured GitHub issues using the `gh` CLI — grounding descriptions in actual repo code where possible, classifying each as bug vs feature, and applying labels that exist on the target repo. Files issues directly without per-item approval; the user reviews in GitHub afterward. Use this skill whenever the user asks to "create issues", "file tickets", "open GitHub issues", "turn these into issues", or hands over a list of things that clearly belong in a tracker. Trigger even when the phrasing is loose ("can you write these up as issues", "file these on the repo", "log this as a bug") as long as GitHub issues are the destination.

Orchestrates a multi-persona code review of the user's current project by spawning parallel sub-agents — each adopting a different reviewer persona (security, performance, WordPress, WooCommerce, frontend/UX, devops, QA) — then synthesizing their findings into a single prioritized, actionable report with severity ratings, deduplicated issues, and decisions-needed flagged for the user. Use whenever the user asks for a code review, code audit, multi-persona review, panel review, second opinion on a codebase, "review this project", "audit this repo", a security + performance + UX pass, or names specific reviewer personas. Trigger on loose phrasing too ("get a few sets of eyes on this", "review my plugin/theme for production", "what would a senior engineer say about this"). The skill auto-detects which personas to run (always runs security/performance/QA; adds WordPress, WooCommerce, frontend/UX, and devops based on signals in the code), writes raw findings and a synthesized report under `.reviews/{timestamp}/` in the project root, and offers follow-ups to render an HTML report or file GitHub issues. Not for single-file targeted bug hunts; not for greenfield design reviews where there is no code yet.

Performs a systematic, evidence-based code audit of WordPress projects — specifically custom must-use (mu) plugins and custom themes — covering security, performance, readability, and UX. Use this skill whenever the user asks for a code audit, code review, security review, performance review, pre-launch review, or general quality pass on a WordPress codebase, or when they mention reviewing/auditing a WordPress plugin, theme, or mu-plugin. Trigger even when the phrasing is loose ("can you look over this theme", "give this plugin a once-over", "is this production-ready") as long as WordPress is in the picture. Default deliverable is a written report — do not modify project files unless the user explicitly asks for fixes.