菜单
Use this skill for non-trivial software changes. It coordinates requirements specification, conceptual modeling, SOLID-guided responsibility assignment, interface design, test specification, TDD construction, and review to avoid procedural implementation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Author or update tool-neutral knowledge packs in ai-knowledge-base.
A workflow for authoring Go tests. Starting from the table-driven test scaffold generated by gotests, it runs the cycle of test design -> adding test cases -> running -> fixing defects. Use when: (1) invoked via /go-test-authoring, (2) asked to "write tests" or "add tests" for Go, (3) asked to implement tests for a Go function or method.
Git commit with Conventional Commits format. Use when user asks to commit changes, says "commit", "/commit", or after completing code changes when explicitly asked to commit.
Create GitHub Pull Request with project's PR template. Use when user asks to create PR, says "create PR", "/pr-create", or after completing implementation when asked to open a pull request.
Address PR review feedback. Collect both unresolved inline comments and review-body comments on a GitHub PR, build a fix plan and turn it into tasks, then work through them one by one (assess -> fix -> commit -> push -> reply). Use when invoked as /pr-review-fix, when asked to "address the review comments" or "respond to PR feedback", or for follow-up work after a PR review.
Internal Structure-Behavior Design skill for conceptual modeling and structure design. Use only as part of the Structure-Behavior Design workflow.
| id | structure-behavior-design.skill.orchestrator |
| kind | skill |
| name | structure-behavior-design-orchestrator |
| description | Use this skill for non-trivial software changes. It coordinates requirements specification, conceptual modeling, SOLID-guided responsibility assignment, interface design, test specification, TDD construction, and review to avoid procedural implementation. |
| tags | ["structure-behavior-design","design","workflow"] |
| tools | {"claude":{"enabled":true}} |
Guide non-trivial software development through structure design and behavior design before implementation.
Do not jump directly from requirement to code.
This workflow prevents:
Use this workflow for:
Do not use the full workflow for:
For small changes that follow an existing design:
Required:
Recommended reviewers:
For changes involving new behavior, interfaces, or multiple files:
Required:
Recommended reviewers:
For public API, database schema, authentication, authorization, billing, contract, migration, or cross-module architecture changes:
Required:
Recommended reviewers:
Before writing production code, produce:
Structure design defines:
Behavior design is performed through tests.
Tests should specify:
Tests should not mirror private implementation details.
For each behavior:
After implementation, review for:
