Skip to content

feat: emphasize the code backlink #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wesnick merged 1 commit into from
May 2, 2026
+3 −3
Merged

feat: emphasize the code backlink #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...spec-anchored-development/skills/spec-anchored-development/references/golang.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,4 +29,4 @@ Use Go-native anchors and ownership boundaries.
- spec -> `cmd/api/`, `internal/service/`, `internal/store/`
- spec -> `pkg/client/` when there is a supported library surface
- spec -> `migrations/`, `api/`, `test/`
- code breadcrumb -> package comment, doc.go, or nearby design README
- code back-link -> `// Spec:` comment per the [canonical back-link format](../SKILL.md#code-to-spec-back-link-format); for package-level ownership, place it in `doc.go`
2 changes: 1 addition & 1 deletion ...spec-anchored-development/skills/spec-anchored-development/references/python.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,4 +28,4 @@ Use Python-native anchors in specs instead of generic pseudocode.
- spec -> `src/package/subsystem/`
- spec -> `app/api/routes.py`
- spec -> `package/services/`, `package/models/`, `tests/`
- code breadcrumb -> package docstring, module header comment, or adjacent README if the repo already uses those patterns
- code back-link -> `# Spec:` comment per the [canonical back-link format](../SKILL.md#code-to-spec-back-link-format); for package-level ownership, place it in `__init__.py`
2 changes: 1 addition & 1 deletion ...-anchored-development/skills/spec-anchored-development/references/typescript.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,4 @@ Use TypeScript-native anchors across backend, frontend, or full-stack repos.

- spec -> `packages/*`, `apps/*`, `src/server/`, `src/lib/`, `src/routes/`
- spec -> `openapi/`, `prisma/`, `migrations/`, `workers/`
- code breadcrumb -> package README, file header, route module comment, or generated doc index already used by the repo
- code back-link -> `// Spec:` comment per the [canonical back-link format](../SKILL.md#code-to-spec-back-link-format)
Loading