clean-commits
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
Browse published AI skills maintained by troykelly. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
128Repository stars across indexed skills
640Repository forks
61Average repository stars per indexed skill
5Repository stars may repeat across skills from the same repository.
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
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.
Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby...
Use before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verified
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
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoid...
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
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 when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra time
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
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...
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
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...
Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
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.
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
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
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.