troykelly
@troykelly
Public Skills
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass
feedback-triage
by troykelly
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-board-enforcement
by troykelly
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.
worker-dispatch
by troykelly
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.
autonomous-orchestration
by troykelly
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.
issue-driven-development
by troykelly
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
autonomous-operation
by troykelly
Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved
github-api-cache
by troykelly
MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.
issue-prerequisite
by troykelly
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
database-architecture
by troykelly
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
postgis
by troykelly
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
by troykelly
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
timescaledb
by troykelly
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
acceptance-criteria-verification
by troykelly
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
api-documentation
by troykelly
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
by troykelly
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
deferred-finding
by troykelly
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
by troykelly
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
environment-bootstrap
by troykelly
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
no-deferred-work
by troykelly
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
issue-decomposition
by troykelly
Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units
epic-management
by troykelly
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.
local-service-testing
by troykelly
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
pr-creation
by troykelly
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
branch-discipline
by troykelly
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
inclusive-language
by troykelly
Use when writing code, documentation, or comments - always use accessible and respectful terminology
error-recovery
by troykelly
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
pre-work-research
by troykelly
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
initiative-architecture
by troykelly
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.
clean-commits
by troykelly
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
pexels-media
by troykelly
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.
memory-integration
by troykelly
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts
features-documentation
by troykelly
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
comprehensive-review
by troykelly
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
inline-documentation
by troykelly
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
conflict-resolution
by troykelly
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
issue-lifecycle
by troykelly
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
milestone-management
by troykelly
Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.
ipv6-first
by troykelly
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.
project-status-sync
by troykelly
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
strict-typing
by troykelly
Use when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time
research-after-failure
by troykelly
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
work-intake
by troykelly
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.
security-review
by troykelly
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
review-gate
by troykelly
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met
style-guide-adherence
by troykelly
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
review-scope
by troykelly
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
verification-before-merge
by troykelly
Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified
tdd-full-coverage
by troykelly
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
issue-prerequisite
by troykelly
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
project-board-enforcement
by troykelly
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.
feedback-triage
by troykelly
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.
epic-management
by troykelly
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.
acceptance-criteria-verification
by troykelly
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
api-documentation
by troykelly
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
by troykelly
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
autonomous-operation
by troykelly
Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved
code-reviewer
by troykelly
Use when explicitly asked to run the code-reviewer subagent or when another skill requires the code-reviewer agent card.
autonomous-orchestration
by troykelly
Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.
branch-discipline
by troykelly
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
database-architecture
by troykelly
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
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
no-deferred-work
by troykelly
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
ipv6-first
by troykelly
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.
code-simplifier
by troykelly
Use when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.
clean-commits
by troykelly
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
inclusive-language
by troykelly
Use when writing code, documentation, or comments - always use accessible and respectful terminology
issue-lifecycle
by troykelly
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
error-recovery
by troykelly
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
code-architect
by troykelly
Use when asked for an architecture blueprint or explicitly asked to run the code-architect subagent.
code-explorer
by troykelly
Use when asked to trace existing codepaths or explicitly asked to run the code-explorer subagent.
deferred-finding
by troykelly
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
review-scope
by troykelly
Use before code review - determine if change is minor (review new code only) or major (review impacted code too)
comment-analyzer
by troykelly
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
postgres-rls
by troykelly
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
pexels-media
by troykelly
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.
issue-decomposition
by troykelly
Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units
project-status-sync
by troykelly
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
memory-integration
by troykelly
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts
initiative-architecture
by troykelly
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.
pr-test-analyzer
by troykelly
Use when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
comprehensive-review
by troykelly
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
research-after-failure
by troykelly
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
features-documentation
by troykelly
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
issue-driven-development
by troykelly
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
security-review
by troykelly
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
pr-creation
by troykelly
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
documentation-audit
by troykelly
Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.
session-start
by troykelly
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
inline-documentation
by troykelly
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
local-service-testing
by troykelly
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
milestone-management
by troykelly
Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.
conflict-resolution
by troykelly
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
environment-bootstrap
by troykelly
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
postgis
by troykelly
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
review-gate
by troykelly
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met
pre-work-research
by troykelly
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
security-reviewer
by troykelly
Use when explicitly asked to run the security-reviewer subagent or when another skill requires the security-reviewer agent card.
silent-failure-hunter
by troykelly
Use when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent.