claude-code-plugins

Add comments, feedback, review notes, or replies to existing JIRA issues. Use when the user wants to post a comment, reply to a discussion, leave review feedback, or add notes on a JIRA ticket. Transforms raw input into clear, well-structured comments. Also use when the user wants to post code review findings or PR review results to a JIRA ticket. Triggers on any request to comment on, reply to, or add feedback to a JIRA issue.

Pull SEO metrics from the DataForSEO API v3 — keyword research (search volume, CPC, keyword difficulty, search intent, keyword ideas), competitor & domain analysis (which keywords a domain ranks for, organic traffic estimates, competitors, keyword gaps, top pages), live Google SERP & rank checking, and backlink profiles (referring domains, anchors, link quality). Use this whenever the user wants SEO data, keyword metrics, search volume, keyword difficulty, SERP positions, rankings, competitor research, traffic estimates, or backlink analysis for any website or project — and especially whenever DataForSEO is mentioned. Routes the request to the right endpoint and runs it via a generic client script using DATAFORSEO_LOGIN / DATAFORSEO_PASSWORD from the environment. Triggers on requests like "how much search volume does X get", "what keywords does competitor.com rank for", "find SEO competitors for my site", "check our Google ranking for Y", "analyze the backlinks of Z", "keyword research for this project", or a

Collaborative Agent Teams code review with cross-reviewer communication, AI Slop detection, and a unified professional report. Use when the user asks to review a PR, review code changes, or run a code review. Spawns a team of independent reviewer teammates (Virtual Mariusz, Backend Solidifier, Frontend Virtuoso, Quality Purist, Security Sentinel, Devil's Advocate) that can communicate with each other and share findings. Produces a professional report with executive summary, AI Slop score, cross-reviewer findings, and verdict.

Smart triage of Agent Teams Review findings into three action groups (Fix Now / Fix Later / Skip) with intelligent grouping and severity verification. Use when the user wants to triage, prioritize, or sort review findings after a code review. Also use when the user asks what to fix first, wants an action plan from a review, or mentions triage, prioritize findings, review priorities, or sort review results. Requires a completed review report from agent-teams-review.

Tighten and declutter an existing document so a human can read it fast — cut filler, repetition, throat-clearing, and marketing fluff while keeping every fact, decision, number, and caveat, and keeping the language natural (no jargon, no telegraphic shortcuts). Use when a document (especially one drafted by AI) is bloated, padded, or slow to skim — e.g. the user says "uporządkuj ten dokument", "to jest za długie", "skróć to ale nie gub treści", "wytnij lanie wody", "this doc is bloated", "cut the fluff", "make this readable", "too verbose", "remove the AI slop" — or just generated a long README / spec / report / proposal / release notes / JIRA description and wants it trimmed. Also trigger right after producing a long document, to offer a tightened pass. Do NOT use for writing a new document from scratch, for summaries that intentionally drop information, for translation, or for editing code.

Poprawia wskazany polski tekst stylistycznie, gramatycznie i interpunkcyjnie tak, żeby brzmiał naturalnie — usuwa „sztuczność" typową dla tekstów generowanych przez AI (kalki z angielskiego, nadużywane zaimki i dzierżawcze, „posiadać", nominalizacje, puste waciki marketingowe, monotonny rytm), poprawia szyk wyrazów oraz polską interpunkcję (przecinki przed że/który/aby, cudzysłów „", półpauzy, liczby, kapitalizacja). Zachowuje sens, ton, rejestr, długość, formatowanie, linki, słowa kluczowe SEO i przeznaczenie tekstu (email, wpis na blog, opis SEO, komentarz, post, ogłoszenie). Używaj zawsze, gdy użytkownik prosi o poprawienie, redakcję, korektę, dopracowanie lub „uczłowieczenie" polskiego tekstu, mówi że coś „brzmi sztucznie", „jak z AI", „nienaturalnie", „drętwo", chce poprawić styl, gramatykę, szyk albo interpunkcję po polsku, dopracować polski email/blog/opis/post, albo wywołuje /polish-correct. Nie tłumacz i nie dopisuj treści — popraw tylko to, co już jest.

Analyze changes and propose CLAUDE.md updates. Accepts an optional argument describing what changed (e.g., `/claude-md we switched from Jest to Vitest`). Use when the user says "update claude.md", "sync claude.md", "document this in claude.md", after finishing a task that introduced new patterns or conventions, when new tools/commands/dependencies were added, or when project architecture changed. Do NOT trigger for simple questions about CLAUDE.md content, reading CLAUDE.md, or general project questions.

Create clean conventional commits. Use when the user wants to commit changes, make a commit, save progress, or says "commit". Offers three message variants (short, descriptive, multi-line) with live preview, automatic task number detection from branch names, and conventional commit prefixes. Never adds Co-Authored-By lines.

Fetch JIRA issues via REST API and save as minimal extracted JSON. Bypasses MCP tools for maximum data efficiency and token minimization. Use when the user wants to download, fetch, pull, export, or cache JIRA data locally. Triggers on requests to fetch issues, download tasks, export JIRA data, get issues from JIRA, pull sprint/version/project data, cache JIRA issues, dump JIRA to file, or any variation like "give me data from JIRA", "I need issues from...", "pull tasks for sprint X", "get me everything from version Y". Also triggers when the user needs JIRA data saved to a file for offline analysis or for other skills to consume. Does NOT use MCP — calls JIRA REST API v3 directly via Node.js script.

Generate detailed release notes for a single Jira version. Transforms technical issues into a professional, business-facing feature overview with categorized items. Use when the user wants release notes, a version summary, a release plan, or a feature overview for a specific version. Triggers on any request mentioning release notes, version summary, release plan, or feature overview.

Generate a condensed project-wide product roadmap from Jira version data. Produces a multi-version overview with theme summaries, highlights, and links to detailed release notes pages. Use when the user wants a product roadmap, project overview, or version overview. Triggers on any request mentioning roadmap, product roadmap, project overview, or version overview.

Generate testing scenarios for a Jira release version. Combines Jira issue descriptions with git diff analysis (Quality vs Master) to produce a concise table of what needs manual testing before release. Use when the user wants testing scenarios, a test plan, QA checklist, release testing guide, or pre-release verification. Triggers on any request mentioning testing release, test scenarios, QA plan, release testing, what to test, pre-release checklist, or testing before deployment.

Generate a daily JIRA summary with intelligent triage and ABCDE priority classification. Groups tasks into Action Needed, Ready to Proceed, and Info categories with actionable summaries. Creates optional Claude Code todo lists for follow-up. Use when the user wants a daily standup summary, task triage, daily review, morning briefing, sprint check-in, or wants to know what needs attention in JIRA today. Triggers on any request mentioning daily summary, standup prep, triage, daily review, morning briefing, what needs my attention, sprint status check, or daily JIRA report.

Interview the user relentlessly about a plan, design, or architecture until every branch of the decision tree is resolved. Use when the user wants to stress-test a plan, get grilled on their design, poke holes in an idea, play devil's advocate, challenge an approach, or says things like "grill me", "what am I missing?", "is this plan solid?", "review my architecture", "tear this apart", or "challenge my thinking". Also use when someone presents a plan and seems uncertain or asks for feedback on a design decision.

Create well-structured JIRA tasks for any software project. Use when the user describes a feature, bug, improvement, or any work item that needs to become a JIRA ticket. Analyzes the project codebase to provide accurate technical details. Always drafts the task for user review before sending to JIRA. Triggers on any request to create a task, ticket, story, bug report, or JIRA issue.

Run a comprehensive multi-agent PR review on code changes. Use when the user asks to review a PR, review code changes, review a branch, run a code review, or check code before merging. Supports git diff comparisons, specific file review, and directory-level review. Orchestrates 7 specialized agents (architecture, code quality, bugs, security, tests, performance, acceptance) in parallel and produces an aggregated report with verdict.