菜单
Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").
Find all FIXME comments across the codebase and fully implement the work they describe. Use when the user asks to fix, resolve, or address FIXME comments, or when running the "fixme" command. Runs a discovery script to find every FIXME, expands multiline comment blocks, groups related FIXMEs across files into a single implementation task, completes the full underlying code changes, removes the FIXME comments only after the work is done, and verifies that no FIXMEs remain.
Validate that reasoning parameters are correctly serialized and sent to provider APIs. Use when the user asks to test reasoning serialization, run reasoning tests, verify reasoning config fields, or check that ReasoningConfig maps correctly to provider-specific JSON (OpenRouter, Anthropic, GitHub Copilot, Codex).
Resolve inline code review comments on a GitHub PR. Use when asked to "resolve review comments", "address PR feedback", "fix PR comments", or "work through review comments". Fetches every inline comment with its surrounding code context, then applies each change systematically.
Generate a Twitter/X post highlighting a Forge feature. Use when the user asks to write a tweet, create a Twitter post, or promote a ForgeCode feature on social media. The post always accompanies an attached video demonstrating the feature.
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
| name | execute-plan |
| description | Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file. |
Execute structured task plans with automatic status tracking and progress updates.
When a plan is provided, all tasks in the plan must be completed. Before starting execution, recite:
"I will execute this plan to completion. All the 20 tasks will be addressed and marked as DONE."
STEP 1: Recite the commitment to complete all tasks in the plan.
STEP 2: Read the entire plan file to identify pending tasks based on task_status.
STEP 3: Announce the next pending task and update its status to IN_PROGRESS in the plan file.
STEP 4: Execute all actions required to complete the task and mark the task status to DONE in the plan file.
STEP 5: Repeat from Step 3 until all tasks are marked as DONE.
STEP 6: Re-read the plan file to verify all tasks are completed before announcing completion.
Use these status indicators in the plan file:
[ ]: PENDING
[~]: IN_PROGRESS
[x]: DONE
[!]: FAILED
[ ] (PENDING) task[~] (IN_PROGRESS)[x] (DONE)