playbooks

home / skills / troykelly

troykelly skills

Find 61 skills from 1 repo created by troykelly on GitHub.

1 repo
61 skills
GitHub

Sponsored

worker-dispatch

troykelly/claude-skills

5
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.
issue-decomposition

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Advertise on playbooks
Reach thousands of developers actively evaluating dev tools, MCP servers, and agent skills. Floating banners, pinned cards, and in-feed placements.
learn more
worker-protocol

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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

troykelly/claude-skills

5
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
research-after-failure

troykelly/claude-skills

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

troykelly/claude-skills

5
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.
documentation-audit

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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.
agent-development

troykelly/claude-skills

5
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 agent development best practices for Claude Code plugins.
session-start

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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.
hook-development

troykelly/claude-skills

5
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, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
features-documentation

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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

troykelly/claude-skills

5
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

troykelly/claude-skills

5
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

troykelly/claude-skills

5
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

troykelly/claude-skills

5
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.
api-documentation

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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
epic-management

troykelly/claude-skills

5
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.
milestone-management

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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
timescaledb

troykelly/claude-skills

5
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

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
Use when writing code, documentation, or comments - always use accessible and respectful terminology
local-service-testing

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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.
project-status-sync

troykelly/claude-skills

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

troykelly/claude-skills

5
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
no-deferred-work

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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
frontend-design

troykelly/claude-skills

5
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.
acceptance-criteria-verification

troykelly/claude-skills

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

troykelly/claude-skills

5
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.
initiative-architecture

troykelly/claude-skills

5
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.
project-board-enforcement

troykelly/claude-skills

5
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.
strict-typing

troykelly/claude-skills

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

troykelly/claude-skills

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

troykelly/claude-skills

5
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.
review-scope

troykelly/claude-skills

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

troykelly/claude-skills

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