session-start
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
发现 测试与安全 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Use at the beginning of every work session - establishes context by checking GitHub project state, reading memory, verifying environment, and orienting before starting work
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcp__memory knowledge graph for persistent facts
Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.
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 asked to evaluate PR test coverage or explicitly asked to run the pr-test-analyzer subagent.
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Setup 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, Typ...
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace
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
Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions
Use when explicitly asked to run the security-reviewer subagent or when another skill requires the security-reviewer agent card.
Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Use when asked for an architecture blueprint or explicitly asked to run the code-architect subagent.
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 asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.
Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state
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...
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 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.
Use when writing code - follow Google style guides where available, otherwise follow established best practices for the language
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。