菜单
Implement a GitHub enhancement issue for the axiforge Electron app. Use when asked to work issue-driven feature requests in this repo, including triage labels, project status updates, branch/PR flow, tests, and manual verification.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fix a GitHub bug issue for the axiforge Electron app. Use when asked to resolve issue-driven bugs in this repo with labels, project tracking, repro tests, branch/PR flow, and manual verification.
Build axiforge locally for beta testing. Use when asked to run the repo's local beta packaging flow, including validation tests, beta version stamping, artifact builds, release creation, and Discord notification.
Run the axiforge release workflow. Use when asked to produce either a beta or official release for this repo, including validation, versioning, packaging, GitHub release steps, and optional extended test suites.
Triage a GitHub issue in the axiforge repo. Use when asked to classify an issue as bug, enhancement, or question before deeper work.
| name | add-feature |
| description | Implement a GitHub enhancement issue for the axiforge Electron app. Use when asked to work issue-driven feature requests in this repo, including triage labels, project status updates, branch/PR flow, tests, and manual verification. |
This skill imports the existing repo workflow from .claude/commands/add-feature.md.
Use it when the user wants Codex to implement GitHub issue #<n> as an enhancement in this repository.
Fetch the issue with gh api repos/darkharasho/axiforge/issues/<n>.
If the issue is missing, stop. If gh is unauthenticated, stop and tell the user to run gh auth login.
Confirm this is an enhancement, not a bug.
If the issue already has a bug label, stop and tell the user to use the bug-fix workflow instead.
If enhancement is missing, add it with gh issue edit.
Compute a stable slug from the issue title. Use the first 4-5 words, lowercase, strip non-alphanumerics except hyphens, minimum 2 words, max 40 chars.
Add the issue to the GitHub project and move it to In progress.
Project ID: PVT_kwHOCJlSRs4BRf9t
Status field ID: PVTSSF_lAHOCJlSRs4BRf9tzg_T1Jg
In progress option ID: 5ef0dc97
Done option ID: 98236657
Capture the project item ID for later.
Post an opening issue comment with the planned approach and branch name feat/issue-<n>-<slug>.
Explore the code before editing. Start from:
src/main/ for data/API worksrc/renderer/ for UI worktests/ for coverage placementCreate or reuse branch feat/issue-<n>-<slug>.
Add tests for the requested behavior before implementing the feature. Run the relevant test command and confirm the new test fails first when practical.
Implement the feature with minimal, targeted changes.
Run tests, fix regressions, and re-run. Use at most two fix-and-retest cycles before reporting failure.
Stop for manual verification before finalizing. Tell the user what changed, how to exercise it, and what to verify. Wait for confirmation before proceeding.
Commit and push:
git add src/ tests/git commit -m "feat: <issue title> (closes #<n>)"git push -u origin feat/issue-<n>-<slug>Open or reuse the PR for that branch and capture the PR URL.
Move the project item to Done and post a closing issue comment with the PR URL.
End by reporting PR opened: <url>.
If implementation or tests remain blocked:
In progress