project-status-sync
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
发现 生活与效率 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
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
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
HARD GATE before PR creation - verifies review artifact exists in issue comments, all findings addressed or tracked, blocks PR creation if requirements not met
Use when writing code, documentation, or comments - always use accessible and respectful terminology
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
MANDATORY before any GitHub project operations - caches project metadata to prevent rate limit exhaustion. Called by session-start. Other skills MUST use cached data.
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...
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
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 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
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 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。