メニュー
Standard workflow for GitHub Copilot coding agents including report_progress usage, delegation handling, and PR communication patterns.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/oocx/tfplan2md --skill coding-agent-workflowコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
Minimum-requirements checklist for any change — code or docs-only. Run this before every PR creation or push to avoid CI failures on the first attempt.
Generate PNG screenshots for release notes using the repository's HtmlRenderer and ScreenshotGenerator tools. Use when asked to add screenshots to release notes or documentation.
Determine the next available issue number across all change types (feature, fix, workflow) by checking both local docs and remote branches, then reserve it by pushing an empty branch.
SKILL.md を表示中
| name | coding-agent-workflow |
| description | Standard workflow for GitHub Copilot coding agents including report_progress usage, delegation handling, and PR communication patterns. |
Provides the standard operational workflow that all GitHub Copilot coding agents must follow when executing tasks in pull requests.
This skill is automatically loaded by all coding agents. It defines the core workflow for:
report_progress toolYou are running as a GitHub Copilot coding agent. Follow this workflow:
GitHub Copilot automatically creates branches and PRs - you do NOT create them:
@copilot, GitHub automatically creates a copilot/* branch and draft PRgit checkout, git switch, or git branch commands - you're already on the right branchreport_progress (which handles git push automatically)Why this fails:
git checkout -b commands will fail (permission denied)For Direct Questions (When Running as Primary Agent): If you are the primary agent on a PR (not delegated via task tool), you can create PR comments to ask the Maintainer questions. Wait for a response before proceeding.
For Delegated Execution (When Invoked via task Tool): If you were invoked by the Workflow Orchestrator via the task tool, you run in an isolated context. In this case:
edit/create tools to apply all file changes - do not just describe changes; actually apply themgit commit to commit your changes — report_progress is NOT available to subagents; use git add <files> && git commit -m "type: message" instead (see step 4 for details)Complete Your Work: Implement the requested changes following your role's guidelines. Use edit/create tools to apply all file modifications — never just describe or list changes without applying them.
Commit and Push Changes:
Primary agent (running the top-level PR): Use the report_progress tool. It handles git add, git commit, and git push automatically with the GitHub Actions token. Manual git push fails (no personal credentials). Call it with:
commitMessage: Conventional commit message (e.g., "feat: add feature X")prDescription: Markdown checklist showing completed and remaining workreport_progress(
commitMessage="feat: implement user authentication",
prDescription="""
- [x] Add authentication service
- [ ] Add authorization middleware
"""
)
Delegated subagent (spawned via task tool): report_progress is NOT available — it exists only in the primary agent's tool context. Use git commit instead:
git add <changed files>
git commit -m "type: description of changes"
# Do NOT run git push — it will fail with HTTP 403
Your commits accumulate in the local branch. When the parent agent calls report_progress, ALL local commits (including yours) are pushed to the remote PR branch.
Create Summary Comment (After Progress Reported): Post a PR comment with:
Note: If you're running in delegated mode (via task tool), include this summary in your response text instead of creating a PR comment.
Example Summary Comment:
✅ Implementation complete
**Summary:** Implemented feature X with tests and documentation
**Changes:**
- Added FeatureX.cs with core logic
- Added FeatureXTests.cs with 15 test cases
- Updated README.md
**Next Agent:** Technical Writer (to review documentation)
**Status:** Ready
report_progress is only available to the primary agent - subagents spawned via task tool must use git commit insteadreport_progress for commits and pushes (primary agent) - never use manual git push commandsgit commit before completing - uncommitted changes will be lost if only in memory; the parent's report_progress can pick up uncommitted files via git add . but this is a fallback, not the primary mechanismedit/create tools to apply file changes - never just describe changes in your response without applying them