All authors
Claude Skills by troykelly
github.com/troykelly130 skills3 installs197 views
- Security ReviewMANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential codeVotes: 0GitHub stars: 11
- Session StartUse at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting workVotes: 0GitHub stars: 11
- Strict TypingUse when writing code in typed languages - enforces full typing with no any/unknown/untyped escapes, even if it requires extra timeVotes: 0GitHub stars: 11
- Style Guide AdherenceUse when writing code - follow Google style guides where available, otherwise follow established best practices for the languageVotes: 0GitHub stars: 11
- Tdd Full CoverageUse when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirementVotes: 0GitHub stars: 11
- TimescaledbMANDATORY 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 CompressVotes: 0GitHub stars: 11
- Verification Before MergeUse before merging PR - final gate ensuring all tests pass, review complete, CI green, and acceptance criteria verifiedVotes: 0GitHub stars: 11
- Work IntakeEntry 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.Votes: 0GitHub stars: 11
- Worker DispatchUse 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.Votes: 0GitHub stars: 11
- Worker HandoverDefines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.Votes: 0GitHub stars: 11
- Worker ProtocolDefines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.Votes: 0GitHub stars: 11
- Code ArchitectUse when asked for an architecture blueprint or explicitly asked to run the code-architect subagent.Votes: 0GitHub stars: 11
- Code ExplorerUse when asked to trace existing codepaths or explicitly asked to run the code-explorer subagent.Votes: 0GitHub stars: 11
- Code ReviewerUse when explicitly asked to run the code-reviewer subagent or when another skill requires the code-reviewer agent card.Votes: 0GitHub stars: 11
- Code SimplifierUse when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.Votes: 0GitHub stars: 11
- Comment AnalyzerUse when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.Votes: 0GitHub stars: 11
- Pr Test AnalyzerUse when asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.Votes: 0GitHub stars: 11
- Security ReviewerUse when explicitly asked to run the security-reviewer subagent or when another skill requires the security-reviewer agent card.Votes: 0GitHub stars: 11
- Silent Failure HunterUse when asked to detect silent failures/weak error handling or explicitly asked to run the silent-failure-hunter subagent.Votes: 0GitHub stars: 11
- Type Design AnalyzerUse when asked to evaluate type design/invariants or explicitly asked to run the type-design-analyzer subagent.Votes: 0GitHub stars: 11
- Agent DevelopmentUse when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.Votes: 0GitHub stars: 11
- Frontend DesignCreate 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 avoids generic AI aesthetics.Votes: 0GitHub stars: 11
- Hook DevelopmentUse when the user wants to create Codex workflow hooks (pre/post run gates, tool-use validators, stop checks) or needs guidance on hook scripts and hooks.json configuration.Votes: 0GitHub stars: 11
- Sentry Code ReviewAnalyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.Votes: 0GitHub stars: 11
- Sentry Setup Ai MonitoringSetup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically detects installed AI SDKs and configures the appropriate Sentry integration.Votes: 0GitHub stars: 11
- Sentry Setup LoggingSetup 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, React, Next.js, and other frameworks.Votes: 0GitHub stars: 11
- Sentry Setup MetricsSetup Sentry Metrics in any project. Use this when asked to add Sentry metrics, track custom metrics, setup counters/gauges/distributions, or instrument application performance metrics. Supports JavaScript, TypeScript, Python, React, Next.js, and Node.js.Votes: 0GitHub stars: 11
- Sentry Setup TracingSetup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and Node.js.Votes: 0GitHub stars: 11
- Skill DevelopmentUse when the user wants to create or refine Codex skills, improve skill descriptions, organize skill resources, or follow Codex skill best practices.Votes: 0GitHub stars: 11
- Acceptance Criteria VerificationUse after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issueVotes: 0GitHub stars: 11
- Api DocumentationUse when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.Votes: 0GitHub stars: 11
- Apply All FindingsUse after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without traceVotes: 0GitHub stars: 11
- Autonomous OperationUse when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achievedVotes: 0GitHub stars: 11
- Autonomous OrchestrationUse 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.Votes: 0GitHub stars: 11
- Branch DisciplineUse before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct baseVotes: 0GitHub stars: 11
- Ci MonitoringUse after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvableVotes: 0GitHub stars: 11
- Clean CommitsUse when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every pointVotes: 0GitHub stars: 11
- Comprehensive ReviewUse after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until completeVotes: 0GitHub stars: 11
- Conflict ResolutionUse when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrityVotes: 0GitHub stars: 11
- Database ArchitectureMANDATORY when designing schemas, writing migrations, creating indexes, or making architectural database decisions - enforces PostgreSQL 18 best practices including AIO, UUIDv7, temporal constraints, and modern indexing strategiesVotes: 0GitHub stars: 11
- Deferred FindingUse 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 processVotes: 0GitHub stars: 11
- Documentation AuditUse when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.Votes: 0GitHub stars: 11
- Environment BootstrapUse for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessionsVotes: 0GitHub stars: 11
- Epic ManagementUse 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.Votes: 0GitHub stars: 11
- Error RecoveryUse when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery stateVotes: 0GitHub stars: 11
- Features DocumentationUse when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.Votes: 0GitHub stars: 11
- Feedback TriageUse 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.Votes: 0GitHub stars: 11
- Inclusive LanguageUse when writing code, documentation, or comments - always use accessible and respectful terminologyVotes: 0GitHub stars: 11
- Initiative ArchitectureUse 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.Votes: 0GitHub stars: 11
- Inline DocumentationUse when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from codeVotes: 0GitHub stars: 11