Skill Creator

troykelly

71 published skills · 82 GitHub stars across the catalog. View on GitHub ↗

acceptance-criteria-verification

troykelly's avatarfrom troykelly★ 1

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

api-documentation

troykelly's avatarfrom troykelly★ 1

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

troykelly's avatarfrom troykelly★ 1

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

autonomous-operation

troykelly's avatarfrom troykelly★ 1

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

autonomous-orchestration

troykelly's avatarfrom troykelly★ 1

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

troykelly's avatarfrom troykelly★ 1

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

ci-monitoring

troykelly's avatarfrom troykelly★ 1

Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable

clean-commits

troykelly's avatarfrom troykelly★ 1

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

comprehensive-review

troykelly's avatarfrom troykelly★ 1

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

conflict-resolution

troykelly's avatarfrom troykelly★ 1

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

deferred-finding

troykelly's avatarfrom troykelly★ 1

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

troykelly's avatarfrom troykelly★ 1

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

environment-bootstrap

troykelly's avatarfrom troykelly★ 1

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

epic-management

troykelly's avatarfrom troykelly★ 1

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.

error-recovery

troykelly's avatarfrom troykelly★ 1

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

features-documentation

troykelly's avatarfrom troykelly★ 1

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

feedback-triage

troykelly's avatarfrom troykelly★ 1

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.

inclusive-language

troykelly's avatarfrom troykelly★ 1

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

initiative-architecture

troykelly's avatarfrom troykelly★ 1

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.

inline-documentation

troykelly's avatarfrom troykelly★ 1

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

ipv6-first

troykelly's avatarfrom troykelly★ 1

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.

issue-decomposition

troykelly's avatarfrom troykelly★ 1

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

issue-driven-development

troykelly's avatarfrom troykelly★ 1

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-lifecycle

troykelly's avatarfrom troykelly★ 1

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