troykelly-claude-skills

Plugin troykelly-claude-skills from marketplace cascade-code-general-misc-2 in joshuarweaver/cascade-code-general-misc-2. Commands read from the repo's manifest — 1 month ago.

Skills (61)

• Agent Development

  This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or

• frontend-design

  Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

• Hook Development

  This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse,

• sentry-code-review

  Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.

• sentry-setup-ai-monitoring

  Setup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically detects installed AI SDKs and configures the appropriate Sentry integration.

• sentry-setup-logging

  Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and other frameworks.

• sentry-setup-metrics

  Setup Sentry Metrics in any project. Use this when asked to add Sentry metrics, track custom metrics, setup counters/gauges/distributions, or instrument application performance metrics. Supports JavaScript, TypeScript, Python, React, Next.js, and Node.js.

• sentry-setup-tracing

  Setup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and Node.js.

• Skill Development

  This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

• acceptance-criteria-verification

  Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue

• api-documentation

  Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.

• apply-all-findings

  Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace

• autonomous-operation

  Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved

• autonomous-orchestration

  Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, monitors with TaskOutput, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.

• branch-discipline

  Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base

• ci-monitoring

  Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass

• clean-commits

  Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

• comprehensive-review

  Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete

• conflict-resolution

  Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity

• database-architecture

  MANDATORY when designing schemas, writing migrations, creating indexes, or making architectural database decisions - enforces PostgreSQL 18 best practices including AIO, UUIDv7, temporal constraints, and modern indexing strategies

• deferred-finding

  Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

• documentation-audit

  Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.

• environment-bootstrap

  Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions

• epic-management

  Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.

• error-recovery

  Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state

• features-documentation

  Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.

• feedback-triage

  Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.

• github-api-cache

  MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.

• inclusive-language

  Use when writing code, documentation, or comments - always use accessible and respectful terminology

• initiative-architecture

  Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.

• inline-documentation

  Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

• ipv6-first

  IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.

• issue-decomposition

  Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units

• issue-driven-development

  Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification

• issue-lifecycle

  Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end

• issue-prerequisite

  Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

• local-service-testing

  Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks

• memory-integration

  Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts

• milestone-management

  Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.

• no-deferred-work

  Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission

• pexels-media

  Source royalty-free images and videos from Pexels API for design, placeholders, or content. Supports search, curated/popular content, collections, multiple resolutions, and ALWAYS creates detailed sidecar metadata files.

• postgis

  MANDATORY when working with geographic data, spatial queries, geometry operations, or location-based features - enforces PostGIS 3.6.1 best practices including ST_CoverageClean, SFCGAL 3D functions, and bigint topology

• postgres-rls

  MANDATORY when touching auth tables, tenant isolation, RLS policies, or multi-tenant database code - enforces Row Level Security best practices and catches common bypass vulnerabilities

• pr-creation

  Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary

• pre-work-research

  Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach

• project-board-enforcement

  MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.

• project-status-sync

  Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields

• research-after-failure

  Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

• review-gate

  HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met

• review-scope

  Use before code review - determine if change is minor (review new code only) or major (review impacted code too)

• security-review

  MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code

• session-start

  Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work

• strict-typing

  Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time

• style-guide-adherence

  Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language

• tdd-full-coverage

  Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement

• timescaledb

  MANDATORY when working with time-series data, hypertables, continuous aggregates, or compression - enforces TimescaleDB 2.24.0 best practices including lightning-fast recompression, UUIDv7 continuous aggregates, and Direct Compress

• verification-before-merge

  Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified

• work-intake

  Entry point for ALL work requests - triages scope from trivial to massive, asks clarifying questions, and routes to appropriate planning skills. Use this when receiving any new work request.

• worker-dispatch

  Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.

• worker-handover

  Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.

• worker-protocol

  Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.

Subagents (2)

• code-reviewer

  MUST BE USED after implementing code changes. Performs comprehensive 7-criteria code review and posts mandatory review artifact to GitHub issue. Invoke proactively before any PR creation.

• security-reviewer

  PROACTIVELY review security-sensitive code. MANDATORY for changes to auth, input handling, API endpoints, database queries, or credential handling. Read-only analysis with OWASP checklist.

MCP servers (4)

• git

  runs: uvx mcp-server-git --repository .

• memory

  runs: npx -y @modelcontextprotocol/server-memory

• github

  runs: npx -y @modelcontextprotocol/server-github

• playwright

  runs: npx -y @playwright/mcp@latest

Hooks (16)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/check-orchestration-sleep.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/validate-pr-creation.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/validate-local-testing.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/validate-pr-merge.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/validate-tests-pass.sh

• PreToolUse
• PreToolUse
• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/security-scan.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/validate-generated-artifacts.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/track-test-results.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/post-pr-creation.sh

• PostToolUse
• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/plan-limit-account-switch.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/check-ci-before-stop.sh

• Stop

Similar plugins