Merge pull request 'fix: formatting + add clawpub reference' (#4) from clawbot/prompts:fix/formatting-and-readme into main
All checks were successful
check / check (push) Successful in 11s

Reviewed-on: #4
This commit was merged in pull request #4.
This commit is contained in:
2026-02-28 11:45:56 +01:00
2 changed files with 11 additions and 2 deletions

View File

@@ -131,6 +131,15 @@ policies change.
When updating policies in this repo, also update the template repos to match When updating policies in this repo, also update the template repos to match
(Makefile targets, Dockerfile conventions, CI workflows, required files, etc.). (Makefile targets, Dockerfile conventions, CI workflows, required files, etc.).
## See Also
- **[clawpub](https://git.eeqj.de/sneak/clawpub)** — Real-world examples,
rationale, and operational lessons from applying these policies with an
[OpenClaw](https://github.com/openclaw/openclaw) AI agent. Includes detailed
documentation on how the interlocking check system (CI → Docker → Makefile →
tests/lint/fmt) works in practice, why checklists complement prose policies,
and failure stories from production use.
## TODO ## TODO
- Add more prompt templates for common development tasks - Add more prompt templates for common development tasks

View File

@@ -240,8 +240,8 @@ last_modified: 2026-02-22
1. When defining custom string-based types (e.g. `type ImageID string`), 1. When defining custom string-based types (e.g. `type ImageID string`),
implement `fmt.Stringer`. Use `.String()` at SDK and library boundaries implement `fmt.Stringer`. Use `.String()` at SDK and library boundaries
instead of `string(v)`. This makes type conversions explicit, grep-able, instead of `string(v)`. This makes type conversions explicit, grep-able, and
and consistent across the codebase. Example: consistent across the codebase. Example:
```go ```go
type ContainerID string type ContainerID string