add-go-test

Agent Skills › authgear/authgear-server › add-go-test

add-go-test

GitHub

指导为Go仓库编写或扩展单元测试，强调先检查现有测试风格（如Convey BDD或标准testing.T），确保风格一致，添加最小化测试文件并运行验证。

.claude/skills/add-go-test/SKILL.md authgear/authgear-server

触发场景

用户要求添加Go单元测试用户要求更新现有Go测试

安装

npx skills add authgear/authgear-server --skill add-go-test -g -y

更多选项

非标准路径

npx skills add https://github.com/authgear/authgear-server/tree/main/.claude/skills/add-go-test -g -y

不安装直接使用

npx skills use authgear/authgear-server@add-go-test

指定 Agent (Claude Code)

npx skills add authgear/authgear-server --skill add-go-test -a claude-code -g -y

安装 repo 全部 skill

npx skills add authgear/authgear-server --all -g -y

预览 repo 内 skill

npx skills add authgear/authgear-server --list

SKILL.md

Frontmatter

{
    "name": "add-go-test",
    "description": "Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.",
    "argument-hint": "<package or behavior>"
}

Follow this skill when adding Go tests.

Critical: Match Existing Test Style First

Always inspect existing *_test.go files in the package first. This repo uses different testing styles in different packages:

Convey (BDD-style): Many packages use github.com/smartystreets/goconvey. Identified by import . "github.com/smartystreets/goconvey/convey" and test structure like:
```
func TestFoo(t *testing.T) {
  Convey("description", func() {
    // assertions here
    So(result, ShouldEqual, expected)
  })
}
```
Standard testing.T: Some packages use plain *testing.T with manual assertions.

When in doubt, use Convey if the package has any imports of it. Convey provides better error messages and matches the repo's BDD conventions.

Workflow

Inspect the package's *_test.go files first to identify the testing style being used.
Match the local test style exactly. Do not mix styles in the same package.
Add the smallest test file that covers the behavior.
Run go test on the affected package. If the change crosses packages or touches shared code, run the narrowest broader test set that proves the change is safe.

Notes

Prefer table-driven tests when the package already uses them.
Keep fixtures local to the test file unless they are reused elsewhere.
If the test requires generated code or assets, rerun the generator before the final test run.
When using Convey, use So() assertions for consistency with the package style, not manual if statements.