troykelly
@troykelly
Public Skills
code-simplifier
by troykelly
Use when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.
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.
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.
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.
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
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.
pre-work-research
by troykelly
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
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
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
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.
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.
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
ci-monitoring
by troykelly
Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable
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
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
environment-bootstrap
by troykelly
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
issue-lifecycle
by troykelly
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
clean-commits
by troykelly
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
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.
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
security-reviewer
by troykelly
Use when explicitly asked to run the security-reviewer subagent or when another skill requires the security-reviewer agent card.
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
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