一键在 Manus 中运行任何 Skill

gowdk-refactor

星标49

分支0

更新时间2026年6月11日 09:40

Simplify or reorganize GOWDK code without changing behavior. Use for deduplication, removing indirection, splitting or merging packages, renaming internals, or cleanup that should leave tests and public contracts untouched.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

cssbruno

cssbruno/GoWDK

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

GOWDK Refactor

No intended behavior change. Prove it.

Baselines

Behavior pins to keep green and unchanged: parser AST goldens (internal/parser/testdata/golden/parse.golden.json), formatter goldens (internal/lang/testdata/format_golden/), generated-app golden (internal/appgen/testdata/generated_go_golden/app.go.golden), buildgen testdata, IR invariants (gwdkir.CheckInvariants), and the diagnostics registry scan (go test ./internal/diagnostics). If a refactor changes any golden, it changed behavior — stop and reclassify.
Package boundaries are documented contracts: docs/engineering/conventions.md (top-level layout, gowdk.go is the only root Go file), docs/engineering/code-quality.md, and ADR 0006 (compiler vs runtime boundary). internal/ is compiler-private; runtime/ and addons/ are imported by generated user apps, so their exported APIs are public.
Cross-module impact: runtime/adapters/{echo,fiber,gin} and runtime/contracts/{natsbroker,redisstream,websocketfanout} are separate Go modules — only scripts/test-go-modules.sh covers them, go test ./... from the root does not.

Core Workflow

Establish current behavior first through existing tests, goldens, docs, or focused code reading.
Add characterization tests before touching fragile or untested behavior.
Move in small steps that can each be reviewed and reverted independently.
Run the same tests before and after each step:

go test ./... && go build ./cmd/gowdk
scripts/test-go-modules.sh        # required when touching runtime/ or addons/
go run ./cmd/gowdk check --ssr examples/pages/*.gwdk examples/ssr/*.gwdk

Guardrails

Keep exported APIs in runtime//addons/, generated output, manifest JSON shapes, and diagnostic codes stable unless the task explicitly includes changing them — then switch to gowdk-language-change or gowdk-generated-output for that part.
Prefer deleting duplication and indirection over adding new abstraction.
No catch-all utils, common, or shared packages.
Do not mix behavior fixes into the refactor; handle them separately via gowdk-bug.

Report

State what moved or got deleted, confirm goldens are byte-identical and which tests pin the preserved behavior, and document any ambiguous behavior and how it was preserved.

同仓库更多 Skills

同仓库

gowdk-pr-body

cssbruno/GoWDK

Write or update a GOWDK pull request title/body. Use for local branches or GitHub PRs that need a concise why/what/verification summary, issue links, migration notes, and generated-output or docs impact.

2026-06-2749

gowdk-version-bump

cssbruno/GoWDK

Bump the GOWDK release version. Use when updating the CLI version, VS Code extension package version, install snippets, release docs, release notes, or validating a 0.x release metadata change.

2026-06-2749

gowdk-docs

cssbruno/GoWDK

Write or update GOWDK documentation across product, engineering, language, compiler, reference, onboarding, examples, and agent guidance.

2026-06-2649

gowdk-language-change

cssbruno/GoWDK

Change GOWDK language syntax or semantics. Use for parser, formatter, lexer, analyzer, diagnostics, `.gwdk` metadata, `view {}` markup, guards, routes, layouts, actions, APIs, `build`, `server`, `paths`, or docs/examples for language behavior.

2026-06-2249

gowdk-review

cssbruno/GoWDK

Review GOWDK code changes, a PR, or a subsystem for correctness and maintainability. Use for code review requests, pre-merge checks, or auditing a diff against GOWDK product and contract rules.

2026-06-2249

gowdk-compiler-internal

cssbruno/GoWDK

Change GOWDK compiler internals without changing public language behavior. Use for AST shape, analyzer passes, IR (`gwdkir`) structure and invariants, lowering, diagnostics registry plumbing, validation order, or compiler performance work.

2026-06-1449

name	gowdk-refactor
description	Simplify or reorganize GOWDK code without changing behavior. Use for deduplication, removing indirection, splitting or merging packages, renaming internals, or cleanup that should leave tests and public contracts untouched.

GOWDK Refactor

No intended behavior change. Prove it.

Baselines

Behavior pins to keep green and unchanged: parser AST goldens (internal/parser/testdata/golden/parse.golden.json), formatter goldens (internal/lang/testdata/format_golden/), generated-app golden (internal/appgen/testdata/generated_go_golden/app.go.golden), buildgen testdata, IR invariants (gwdkir.CheckInvariants), and the diagnostics registry scan (go test ./internal/diagnostics). If a refactor changes any golden, it changed behavior — stop and reclassify.
Package boundaries are documented contracts: docs/engineering/conventions.md (top-level layout, gowdk.go is the only root Go file), docs/engineering/code-quality.md, and ADR 0006 (compiler vs runtime boundary). internal/ is compiler-private; runtime/ and addons/ are imported by generated user apps, so their exported APIs are public.
Cross-module impact: runtime/adapters/{echo,fiber,gin} and runtime/contracts/{natsbroker,redisstream,websocketfanout} are separate Go modules — only scripts/test-go-modules.sh covers them, go test ./... from the root does not.

Core Workflow

Establish current behavior first through existing tests, goldens, docs, or focused code reading.
Add characterization tests before touching fragile or untested behavior.
Move in small steps that can each be reviewed and reverted independently.
Run the same tests before and after each step:

go test ./... && go build ./cmd/gowdk
scripts/test-go-modules.sh        # required when touching runtime/ or addons/
go run ./cmd/gowdk check --ssr examples/pages/*.gwdk examples/ssr/*.gwdk

Guardrails

Keep exported APIs in runtime//addons/, generated output, manifest JSON shapes, and diagnostic codes stable unless the task explicitly includes changing them — then switch to gowdk-language-change or gowdk-generated-output for that part.
Prefer deleting duplication and indirection over adding new abstraction.
No catch-all utils, common, or shared packages.
Do not mix behavior fixes into the refactor; handle them separately via gowdk-bug.

Report

State what moved or got deleted, confirm goldens are byte-identical and which tests pin the preserved behavior, and document any ambiguous behavior and how it was preserved.