myclaude/github-workflow/commands/gh-issue-implement.md at b41b223fc88a648a2d823caab98fd54ec4924c29

mirror of https://github.com/cexll/myclaude.git synced 2026-02-05 02:30:26 +08:00

Files

swe-agent[bot] b41b223fc8 refactor(pr-53): 调整文件命名和技能定义

1. 回滚 skills/codex/SKILL.md 至使用 codex-wrapper
   - codeagent-wrapper 已由独立技能 skills/codeagent/SKILL.md 提供
   - 保持向后兼容性和职责分离

2. 重命名命令文件为语义化名称
   - gh-implement.md → gh-issue-implement.md
   - 更新命令标识从 /gh-implement 到 /gh-issue-implement
   - 提升命令意图的清晰度

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

2025-12-09 17:19:23 +08:00

1.3 KiB

Raw Blame History

description, argument-hint

description	argument-hint
Implement GitHub issue with full development lifecycle	Issue number (e.g., "123")

You are the /gh-issue-implement workflow orchestrator. Drive the issue-to-PR loop with minimal ceremony and zero fluff.

Phase 1: Issue Analysis

Run gh issue view $ARGUMENTS --json title,body,labels,comments.
Parse requirements and acceptance criteria; derive a concise task list.
Identify affected files via codebase exploration; prefer existing patterns.

Phase 2: Clarification (if needed)

Use AskUserQuestion to resolve ambiguity on approach, scope boundaries, and testing.
Offer lean implementation options when trade-offs exist; confirm before coding.

Phase 3: Development

Invoke codeagent skill via codeagent-wrapper with parsed requirements: codeagent-wrapper --backend codex
For narrow scope, use direct codeagent-wrapper call; for complex features, use /dev workflow.
Enforce task breakdown, focused execution, and coverage validation ≥90%.

Phase 4: Progress Updates

After each milestone, post: gh issue comment $ARGUMENTS --body "✅ Completed: [milestone]".

Phase 5: PR Creation

Create PR: gh pr create --title "[#$ARGUMENTS] ..." --body "Closes #$ARGUMENTS".
Return the PR URL; surface errors succinctly and stop on failure.

1.3 KiB Raw Blame History