Loading...
Loading...
Found 487 Skills
Commit message conventions, staging practices, and commit best practices. Covers conventional commits, explicit staging workflow, logical change grouping, humble fact-based communication style, and automatic issue detection. Use when user mentions committing changes, writing commit messages, git add, git commit, staging files, or conventional commit format.
Full-process specification for software development, covering requirements analysis, design, pre-development, development, testing, and delivery, including review mechanisms, coding specifications and Git workflow
合并 - Complete PR lifecycle: worktree → implement → commits → PR → verify → merge. 触发条件/Triggers: 需要实现功能并提交 PR、修复 Issue、或完成代码审查后的合并工作。 工作流/Workflow: - 阶段 0/Phase 0: 创建工作树/Create worktree - 阶段 1/Phase 1: 实现功能/Implement feature - 阶段 2/Phase 2: 创建 PR/Create PR - 阶段 3/Phase 3: 验证循环/Verification loop (CI + Review + Approval) - 阶段 4/Phase 4: 合并清理/Merge & cleanup 命令/Commands: - /合并 <任务> - 启动完整 PR 工作流 - /合并 create <任务> - 创建 PR - /合并 check - 检查验证状态 - /合并 status - 查看 PR 状态 - /pr <task> - English command 能力/Capabilities: 工作树管理、功能实现、原子提交、PR 创建、验证循环、合并清理。
Create a high-quality pull request: branch, focused changes, lint/build, conventional commit, and a clear PR description with validation steps. Use when the user asks to open or prepare a PR.
Review recent repository changes and decide whether AGENTS.md or other project-level documentation needs a high-level update. Use when finishing a feature, fix, refactor, or architectural change and you need to preserve repo-shaping guidance such as new patterns, constraints, workflows, validation rules, or onboarding-relevant gotchas without adding low-level implementation detail.
Fix GitHub issues end-to-end — from analysis through branch creation, implementation, testing, and PR submission. Use this skill whenever the user mentions fixing a GitHub issue, resolving a bug from an issue tracker, working on a GitHub issue number, or says things like "fix issue
[Hyper] Create one or more Conventional Commits from the current repository state. Inspect staged and unstaged changes, group them into logical change sets, generate a compliant message per group, and commit each group separately in sequence.
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal implementation is done and code needs to be shipped.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
Generate concise Git commit messages in imperative mood. Analyzes staged changes first; if none, examines unstaged and untracked files. Use when the user asks to create, write, draft, make, or generate a commit message.