troykelly
@troykelly
Public Skills
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.
tdd-full-coverage
by troykelly
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
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
verification-before-merge
by troykelly
Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified
issue-lifecycle
by troykelly
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
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.
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.
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.
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
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
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
acceptance-criteria-verification
by troykelly
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
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
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
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.
pre-work-research
by troykelly
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
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.
inclusive-language
by troykelly
Use when writing code, documentation, or comments - always use accessible and respectful terminology
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
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
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.
style-guide-adherence
by troykelly
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
comprehensive-review
by troykelly
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
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