All authors
Claude Skills by Gusen1453
github.com/Gusen145313 skills0 installs28 views
- Plans> **For agents:** Use Creed **tdd** + **test-design** per task. Optional: Superpowers subagent-driven-development / executing-plans. **Goal:** 新增 `skills/issue/` 技能，让 agent 能把一个想法或缺陷变成平台上一条可追踪、可回链、别人能接手的 issue（自带三档模板、创建前先搜重、只映射仓内已有标签、给分支名建议）。 **Architecture:** **无新边界。** 技能是同级文本单元，彼此不 import；唯一的跨单元接口是四处"薄耦合"（grill 网关 / write-spec header / commit-and-push 的 `Closes` 与 voice / using-creed 的清单），全是单向的文本引用，不存在 A→B→A。所以 **solid 门跳过**（这也是 spec §6「接口约定」那一节存在的意义：它替 solid 把箭头方向写死了）。 **Tech Stack:** 纯 Ma...Votes: 0GitHub stars: 3
- Commit And PushUse when the user asks to commit, push, commit-and-push, open/draft a PR/MR, write a PR description with a Test plan, or tag/cut a release — especially when changes should be split into logical commits, or when tempted to dump everything into one commit or push to a protected branch.Votes: 0GitHub stars: 3
- DebugUse when hitting a bug, a test or CI failure, unexpected behavior, or when about to claim something is fixed and the root cause is not yet proven with evidence.Votes: 0GitHub stars: 3
- ExploreUse when a task modifies or references existing code — refactors, legacy rework, reusing a pattern, or when the prompt names specific methods/classes/tables. Harvests repo facts and verifies the user's technical claims before any design or code, so grill only asks judgment calls.Votes: 0GitHub stars: 3
- GrillUse when starting any creative work — a new feature, behavior change, architecture decision, or non-trivial plan — or when the user says grill / grill-me / brainstorm / pressure-test a design, and no code should be written until the design is agreed.Votes: 0GitHub stars: 3
- IssueUse when the user wants to record or file something as an issue — "记一下这个 bug", "提个 issue", "这个先放着", a bug report, a feature request, or anything that should become a trackable GitHub/GitLab issue rather than be acted on now. Composes the draft from the repo's templates or the built-in ones, searches for duplicates first, and asks before creating.Votes: 0GitHub stars: 3
- ReviewUse when finishing a task or task slice, before a merge or PR, or after a major change — and when reviewing a spec, plan, or structure/boundary decision as its own object. Routes each review object to a dedicated rubric reference.Votes: 0GitHub stars: 3
- SolidUse when locking module boundaries, class/API shape, or dependency direction after a design/spec is clear; when new packages, ports, or IO edges are about to be planned; when unit tests need many mocks; or when a review/refactor shows coupling or God-class smell. Do not use as the main skill while product decisions are still open (that is grill).Votes: 0GitHub stars: 3
- TddUse when implementing any feature, bug fix, refactor, or behavior change, before writing production code.Votes: 0GitHub stars: 3
- Test DesignUse when writing, reviewing, or modifying unit/integration tests, adding test cases, assertions, or mocks, or deciding whether a piece of code is worth testing — especially when tempted to add tests for coverage, over-mock dependencies, or write formalistic tests that just restate the implementation.Votes: 0GitHub stars: 3
- Using CreedUse when starting any conversation in a Creed-enabled workspace, or when unsure which Creed skill applies, before any creative, test, debug, or ship work.Votes: 0GitHub stars: 3
- Write PlanUse when you have an approved design or spec, or clear requirements for multi-step work, before touching production code, or when the user asks for an implementation plan or task breakdown.Votes: 0GitHub stars: 3
- Write SpecUse after design alignment (grill), or when the user asks for a design/spec/PRD doc, or when locking scope before an implementation plan, or when handing work off to someone who was not in the design discussion.Votes: 0GitHub stars: 3