troykelly

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

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

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

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

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

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.

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

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

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

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

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

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