一键导入
example-skill
One-sentence description of what this skill does and when to invoke it via /example-skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
One-sentence description of what this skill does and when to invoke it via /example-skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Repeatable codebase audit & fix cycle using parallel agent teams. Phases: audit, consolidate, fix, validate. All output stays in docs/.tmp/ (gitignored, never committed). Supports delta-scoped audits via --since=<tag> to review only changed files and their adjacent code paths (cost-effective for continuous use).
Conducts a relentless interview about every aspect of a plan or idea, walking down each branch of the design tree until shared understanding is reached. Invoke with /grill-me before starting any significant design or implementation work.
Converts a PRD (Forgejo issue or local file) into independently executable Forgejo issues organised as vertical slices through integration layers. Invoke with /prd-to-issues <issue-url-or-path>.
Implements a feature or fix using strict red-green-refactor TDD cycles. Confirms interfaces and behaviours before writing any code. Invoke with /tdd <task description>.
Transforms a conversation or idea into a Product Requirements Document (PRD) with user stories, then submits it as a Forgejo issue. Invoke with /write-a-prd when ready to formalise a feature or initiative.
Refresh .abstract.md (L0) and .overview.md (L1) across all subsystems. Diff mode (default) updates only subsystems modified since the last index; regeneration mode rewrites everything. Invoke with /context-update when indexes may be stale, before running the large task planning protocol, or after significant refactors.
| name | example-skill |
| description | One-sentence description of what this skill does and when to invoke it via /example-skill. |
| context | fork |
| allowed-tools | ["Bash","Read"] |
Brief description of what this skill accomplishes and what problem it solves.
Note: Skills run in an isolated context (
context: fork). They do not share the parent session's conversation history. Pass all required context in the task description when invoking.
One sentence — what condition triggers this skill. Invoked with /<skill-name>.
Describe what information this skill needs to run. The user or orchestrator should provide these when invoking:
<input-1>: what it is and where to find it<input-2>: what it is and where to find it# Step 1: describe what this does
<command>
# Step 2: describe what this does
<command>
Skills can include supporting files in this directory alongside SKILL.md:
example-resource.md — shows the pattern; replace with real resourcesReference supporting files with relative paths: ./example-resource.md.
What a successful invocation produces. Be specific so the user knows when the skill completed correctly.