Discover Blockchain skills, compare source repositories and read the instructions for each workflow.
Laravel testing with PHPUnit and Dusk, feature tests, unit tests, browser tests, factories, assertions. ALWAYS activate when: writing tests, tests/Feature/, tests/Unit/, tests/Browser/, running php artisan test...
Use when generating or updating Table of Contents in markdown files. Supports multiple files, glob patterns, configurable header levels, and various insertion modes. Triggered by "generate toc", "update toc", "...
Translate raw input into structured requirements and route to correct artifacts.
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Addi...
Remove AI-generated code slop from current branch
Run Opengrep static analysis for fast security scanning with open-source rules. Use when scanning with truly open-source SAST, avoiding proprietary rule licenses, using community rules freely, or requiring comm...
Run Semgrep static analysis for fast security scanning and pattern matching. Use when asked to scan code with Semgrep, write custom YAML rules, find vulnerabilities quickly, use taint mode, or set up Semgrep in...
Run Gitleaks for hardcoded secrets detection in code and git history. Use when scanning for API keys, passwords, tokens, certificates, or sensitive credentials in source code and commit history.
Fix GitHub PR review comments using the gh CLI: fetch review threads, implement requested changes, run the full test suite, commit and push fixes, then resolve the review threads. Use when asked to address PR c...
Guide for creating, editing, and understanding justfiles - the command runner inspired by make. Use when: (1) Creating a new justfile for a project, (2) Adding or modifying recipes in an existing justfile, (3)...
This skill should be used when updating the project CHANGELOG, tracking requirement changes, recording design decisions, or documenting version history. Uses git-diff to detect and categorize changes to both co...
systematic code review for correctness, security, style, and performance. Use this when the user asks for a review or before committing significant changes.
Apply UI and accessibility patterns. Uses accessibility, user-experience; invokes @designer, @reviewer for UI and a11y.
Apply language and framework coding standards. Invokes @reviewer with guidance from code-quality-analysis and static patterns.
Idiomatic Go patterns review. Use when checking Go-specific idioms, interface design, or pointer usage. Ensures code follows Go conventions and best practices.
Go error handling review. Use when checking error wrapping, context propagation, or error checking patterns. Ensures proper error chains, context usage, and nil checks.
Detects and safely removes unused code (imports, functions, classes) across multiple languages. Use after refactoring, when removing features, or before production deployment. Includes safety checks and validat...
Project-wide coding standards and conventions specialist. Use PROACTIVELY when writing code, making architectural decisions, or establishing project conventions. Covers coding style, commenting, error handling,...
Claudeの能力を拡張する新規/既存スキルの設計・更新に使うガイド。専門知識、ワークフロー、ツール連携を備えたSkillを作るときに使用する。
This skill should be used when demonstrating skill structure and format. Provides example patterns for creating new skills.
GitHub Issues and Projects v2 management via gh CLI; triggers on 'github', 'create issue', 'list issues', 'github project', 'project board', 'sync tasks'.
Summarize today's git commits into plain-language work updates for Slack. Translates technical changes into what colleagues understand - no coding jargon, sounds like manual work you did yourself.
This skill should be used when the user asks to "review for production", "check production readiness", "evaluate resilience", "assess observability", "review ops", "run chaos experiments", or discusses deployme...
Create clear, effective engineering design documents following structured templates. Use when writing technical design docs for software implementations with problem statement, solution, and alternatives.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.