Manage repositories, check pipelines, review PRs, and collaborate on Bitbucket

Blind peer review for code - multiple agents critique independently, then synthesize privately to avoid groupthink

Parallelizes multi-issue sprints by running independent Claude agents in isolated git worktrees. Each agent creates a PR, self-reviews to 10/10 with 100% issue coverage, then PRs are sequentially merg

Create a detailed prompt for generating high-quality blog posts

'Review and improve the blog post draft for clarity, engagement, and authentic voice.'

Review and improve English translations in bilingual blog posts. Use when the user wants to review, edit, or polish English text in blog posts that have Japanese originals with `::ja` and `::en` sections.

Validate blog posts for quality, consistency, en-GB spelling, and ScottInk style. Use when reviewing posts before publication.

Streamline the daily blog post creation process by automating research, drafting, and style review in a single command.

blog-publishing

blog-voice-review

Citation formatting for law reviews and legal scholarship per *The Bluebook: A Uniform System of Citation* (21st ed. 2020).

Research phase for blueprint workflow - toolbox resolution, lessons discovery, and parallel research agents

Hardens designs and implementations with structured security reviews.

Execute editing workflow orchestration - reviews and polishes completed sections

Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.

Static analysis security vulnerability scanner for Ruby on Rails applications. Use when analyzing Rails code for security issues, running security audits, reviewing code for vulnerabilities, setting up security scanning in CI/CD, managing security warnings, or investigating specific vulnerability types (SQL injection, XSS, command injection, etc.). Also use when configuring Brakeman, reducing false positives, or integrating with automated workflows.

Safely review and merge remote branches into stable. Trigger when: (1) reviewing open PRs, (2) integrating feature branches, (3) checking for stale branches with potential conflicts.

Defines branch naming conventions for issue work. Use when creating branches for issues, understanding work status from branches, or linking commits to issues.

Review code changes on a feature branch compared to a base branch (default: master). Checks for pattern consistency, code duplication, unnecessary variables, and proper use of existing utilities. Use when you want a thorough code review before merging.

Generate brand identity options from brief - marks, colors, typography

Unified brand compliance validation across visual, verbal, and legal dimensions. Use when relevant to the task.

Scan documents and slides for off-brand colors, fonts, and logos. Validate against brand guidelines and suggest corrections.

Use to manage brand guidelines, approvals, and ongoing refresh cadence.

Use to review voice, visual, legal, and partner requirements before publishing

[Design System] Lightweight brand guidelines enforcement for UI copy and visual motifs. Use when (1) checking UI labels/buttons/error messages against brand tone, (2) validating color usage in specific contexts, (3) ensuring reserved components are used correctly, (4) user asks to 'check brand guidelines', 'validate brand compliance', 'review copy tone', or 'enforce design rules'.

brand-legal-review

Create or update project brief through interactive discovery. Use when starting any new idea, revisiting an idea after time away, or when vision feels unclear.

Standard structure and style for sales call briefings including templates for full briefings and quick-reference cheat sheets. Triggers when generating or formatting prospect briefings.

Use this skill when creating, modifying, or reviewing API endpoints and routes. This includes SDK routes (/v1/*), Dashboard routes (/api/v1/*), request/response structures, input validation, OpenAPI documentation, or API-related middleware.

Use this skill when implementing, reviewing, or debugging error handling in the Brokle codebase. This includes repository error mapping, service layer AppError constructors, handler response mapping, domain alias imports, or understanding the industrial error handling flow.

Use this skill when writing, reviewing, or improving tests for the Brokle platform. This includes creating service tests, domain tests, integration tests, or understanding what to test versus what to skip based on the pragmatic testing philosophy.

Rules for effectively utilizing Chrome's browser APIs, including error handling and scheduling tasks.

Systematically tests UI functionality, validates design fidelity with AI visual analysis, monitors console output, tracks network requests, and provides debugging reports using Chrome DevTools MCP. Use after implementing UI features, for design validation, when investigating console errors, for regression testing, or when user mentions testing, browser bugs, console errors, or UI verification.

This skill should be used when users need to capture screenshots of web pages. It supports full-page screenshots, viewport-specific captures, responsive screenshots across multiple device sizes, and element-specific screenshots. Use this skill for visual testing, documentation, design reviews, or any task requiring automated browser screenshots.

Context tracking and plan enforcement system. Use when working on long coding sessions with plans.

This skill should be used when extracting structured data from scientific PDFs for systematic reviews, meta-analyses, or database creation. Use when working with collections of research papers that need to be converted into analyzable datasets with validation metrics.

Unvarnished technical criticism combining Linus Torvalds' precision, Gordon Ramsay's standards, and James Bach's BS-detection. Use when code/tests need harsh reality checks, certification schemes smell fishy, or technical decisions lack rigor. No sugar-coating, just surgical truth about what's broken and why.

Use when reallocating spend across channels/ad sets or setting guardrails

Detects bugs, logic errors, and edge case handling issues in code. Use when reviewing code for runtime errors, null/undefined handling, type errors, and edge cases. Returns structured bug reports with file paths, line numbers, and suggested fixes.

Bug Fix Agent - Automated bug fixing with review loopback and auto-commit to main branch. Fixes bugs, tests them, reviews quality, and commits when quality gates pass.

You are an expert code reviewer. Your role is to independently review fix plans produced by another agent and identify issues, gaps, or risks.

Reproduce, isolate, and fix a bug (or failing build/test), then summarize root cause, fix, and verification steps. Use when the user reports a bug, regression, or failing build/test and wants a fix.

Discover edge cases and test coverage gaps through systematic analysis. Use when analysing test coverage, finding bugs, hunting for edge cases, or when code-reviewer identifies test gaps.

Foundational knowledge for writing BUGS/JAGS models including precision parameterization, declarative syntax, distributions, and R integration. Use when creating or reviewing BUGS/JAGS models.

Generate reference docs, build Sphinx documentation, and review all screenshots

Enforces rules for creating and managing build notes files within the /ProjectDocs/Build_Notes/ directory, including naming conventions, content structure, and update frequency.

Build tools expert including Vite, Webpack, and bundler configuration

Builder user experience systems for Three.js building games. Use when implementing prefab/blueprint save/load, undo/redo command patterns, ghost preview placement, multi-select, or copy/paste building mechanics. Covers the UX layer that makes building feel responsive and intuitive.