Menü
Use when you need build, test, or dev commands for memory-service across Go, Java, frontend, or Python modules.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Batch, validate, and consolidate open Dependabot pull requests for memory-service. Use when asked to inspect the Dependabot queue, verify dependency PRs efficiently, reproduce dependency-update CI failures, combine compatible dependency PRs, or create a validated consolidated dependency PR.
Implement or review Memory Service backend operational logging. Use for REST or gRPC boundaries, provider errors, error wrapping, background workers and task attempts, indexers and maintenance jobs, SSE or gRPC streams, request correlation, and changes under internal/operationevent.
Prepare Memory Service changes for pull request submission. Use whenever Codex is asked to create, open, submit, publish, or ready a pull request, or to perform final PR preflight. Require `task generate` before the final PR commit so generated sources and repository-wide formatting are included.
Use when writing or debugging tests for memory-service. Covers Cucumber BDD patterns and failure reporting.
Use when writing or editing enhancement documents in docs/enhancements/. Provides format, conventions, and numbering guidance.
Use when making changes to the OpenAPI contract. Workflow for updating spec and regenerating clients.
| name | build-test |
| description | Use when you need build, test, or dev commands for memory-service across Go, Java, frontend, or Python modules. |
Use the smallest verification that matches the files you changed.
go build ./...
go test ./internal/plugin/store/sqlite -count=1
task test:go
task dev:memory-service
Use task test:go for the supported full Go test matrix. It deliberately runs
production-auth tests and raw-bearer fixture tests separately:
sqlite_fts5.sqlite_fts5 and auth_testfixtures.go test ./internal/bdd -run TestFeaturesSQLite uses production auth
and fails fixture-based scenarios with raw bearer user assertions are not accepted in production builds.For a targeted SQLite BDD runner that uses the feature-suite bearer fixtures:
CGO_ENABLED=1 go test -race -tags='sqlite_fts5 auth_testfixtures' \
./internal/bdd -run '^TestFeaturesSQLite$' -count=1
For the production-auth BDD runners, match task test:go:
CGO_ENABLED=1 go test -race -tags='sqlite_fts5' ./internal/bdd \
-run 'TestFeaturesPg(APIKeys|Keycloak|KeycloakAuthClients)$' -count=1
./java/mvnw -f java/pom.xml compile
./java/mvnw -f java/pom.xml test
cd frontends/chat-frontend
npm run lint
npm run build
cd frontends/developer
npm run lint
npm run build
python3 -m compileall python
task verify:python
go build ./... > build.log 2>&1
rg -n "ERROR|FAIL|panic|undefined:" build.log
task test:go > test.log 2>&1
rg -n "ERROR|FAIL|panic|--- FAIL:" test.log