clean-commits
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
发现 databases git workflows 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point
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
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
Defines context handover format when workers hit turn limit. Posts structured handover to GitHub issue comments enabling replacement workers to continue seamlessly.
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
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 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 after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
Use to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, and handles worker lifecycle.
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
Use to keep GitHub Project fields synchronized with actual work state - updates status, verification, criteria counts, and other project-specific fields
Use after completing implementation - create pull request with complete documentation, proper labels, linked issues, and verification summary
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
Run focused `kit` CLI commands (file-tree, symbols, search, semantic discovery, dependency analysis, and exports) to build high-signal repository context fast. Use when you need to understand an unfamiliar code...
Creates commits following project conventions. Handles Conventional Commits with project-specific scopes, PR title requirements, changesets for releases, and CI validation rules.
验证GOAL的source_vs追溯链完整性,确保每个GOAL都能追溯到原始VS。当GOAL创建完成后使用。
GitHub CLI operations
Always use this skill to provide context on the codebase. Automatically initializes and references the Speculate documentation framework (coding rules, shortcuts, templates, and project specs) to ensure agents...
Concise, PR-friendly telemetry reports scoped to current branch lifetime. For CI/automation.
Commit and push code with automatic task discovery. Finds completed tasks from the planning board since last commit and includes them in the commit message.
Analyze a specific directory (e.g. frontend/, backend/, e2e/) and generate .claude/rules/ markdown files for it. Use when asked to create rules, analyze a folder for Claude Code, or set up domain memory for a s...
Enhanced cat clone with syntax highlighting, Git integration, and automatic paging for efficient file content viewing. Use this skill when viewing source files, documentation, or when syntax highlighting would...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。