Search

PythonReactSEOPDF

Testing & security AI Skills

Discover Testing & security skills, compare source repositories and read the instructions for each workflow.

Categories: Testing & security

Showing 32,617–32,640 of 81,973

Testing & security Clear filters

Browse skills

GitHub

local-service-testing

troykelly

Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks

GitHub

research-after-failure

troykelly

Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming

GitHub

issue-prerequisite

troykelly

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

GitHub

postgis

troykelly

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

GitHub

api-documentation

troykelly

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

GitHub

environment-bootstrap

troykelly

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

GitHub

conflict-resolution

troykelly

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

GitHub

worker-dispatch

troykelly

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.

GitHub

error-recovery

troykelly

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

GitHub

deferred-finding

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

GitHub

style-guide-adherence

troykelly

Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language

GitHub

tdd-full-coverage

troykelly

Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement

GitHub

review-gate

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

GitHub

inclusive-language

troykelly

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

GitHub

github-api-cache

troykelly

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

GitHub

skill-development

troykelly

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, prog...

GitHub

comprehensive-review

troykelly

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

GitHub

security-review

troykelly

MANDATORY for security-sensitive code changes - OWASP-based security review with dedicated checklist, required before PR for auth, input handling, API, database, or credential code

GitHub

issue-driven-development

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

GitHub

work-intake

troykelly

Entry 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.

GitHub

no-deferred-work

troykelly

Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission

GitHub

sentry-setup-ai-monitoring

troykelly

Setup 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 dete...

GitHub

issue-lifecycle

troykelly

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

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.

More filters

Popularity

Popular tags