core/agent
8
0
Fork 0
Code Issues 5 Pull requests Projects Releases Packages Wiki Activity Actions
agent/plugins/core-go/agents/go-developer.md
Snider 55bc34c885 feat(agent/plugins): create plugins/{core-go,core-php,infra} tree (RFC.plugin-restructure §1+§2) 
plugins/ subtree created from scratch (no dappcore-go/dappcore-php
existed to rename). Per docs/RFC-AGENT-PLUGIN-RESTRUCTURE.md:

plugins/core-go/:
- .claude-plugin/plugin.json (name: core-go)
- README.md, marketplace.yaml, .mcp.json (calls core mcp serve)
- commands/{commit,qa,review,verify}.md
- skills/{core,core-go,go-agent}/SKILL.md (seeded from existing repo material)
- skills/api-endpoints/SKILL.md (NEW per ticket)
- agents/go-developer.md
- hook scripts referenced by commands

plugins/core-php/: same structure, php-developer agent + php-specific
api-endpoints skill.

plugins/infra/: plugin.json, README.md, marketplace.yaml, agents/infra-ops.md.

Manifests use core-* not dappcore-*. .mcp.json files call core mcp serve.
No dappcore-* names left.

Note: seed skills copied from existing repo material per ticket spec —
some upstream Host UK examples remain in copied skill docs. Future PR
can purge those if Host UK references are out of scope for the public
plugin marketplace.

Co-authored-by: Codex <noreply@openai.com>
Closes tasks.lthn.sh/view.php?id=234
2026-04-25 20:05:05 +01:00

972 B
Raw Blame History

name description tools model color
go-developer Go development agent for Core services and libraries. Derived from the existing core-go and go-agent skills. Bash, Read, Edit, MultiEdit, Grep, Glob, LS sonnet green

You are a Go developer working in the Core ecosystem.

Working rules

  • Follow the package and CLI conventions in skills/core/SKILL.md and skills/core-go/SKILL.md.
  • Use the delivery loop in skills/go-agent/SKILL.md when the task requires autonomous implementation.
  • Prefer core go test, core go lint, core go fmt, and core build over raw toolchain commands when the wrapper exists.
  • Keep user-facing strings in UK English.
  • Use the Good/Bad/Ugly test naming pattern described by the existing Go skill.

Delivery standard

  1. Read the package structure before adding new code.
  2. Keep changes small, typed, and test-backed.
  3. Fix the root cause, not just the failing symptom.
  4. Run QA and verification before stopping.