Menu
Use when writing or debugging tests for memory-service. Covers Cucumber BDD patterns and failure reporting.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
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 you need build, test, or dev commands for memory-service across Go, Java, frontend, or Python modules.
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.
Based on SOC occupation classification
| name | testing |
| description | Use when writing or debugging tests for memory-service. Covers Cucumber BDD patterns and failure reporting. |
For REST and gRPC tests, use the Go BDD suite under internal/bdd/testdata/features*/ instead of unit tests with mocks.
Reserve unit tests with mocks for internal implementation details and infrastructure testing.
When tests fail:
go test ./internal/bdd -run TestFeatures... > test.log 2>&1
rg -n "FAIL|ERROR|panic|--- FAIL:" test.log
Prefer searching the redirected log for the failing scenario and stack trace context.
The gRPC text-protobuf helper rewrites quoted canonical users such as "alice"
to scenario-isolated IDs. When production authentication metadata must match a
user ID embedded in a protobuf body (for example user/<id> memory namespaces),
set the metadata from TestScenario.IsolatedUser rather than using a literal
canonical name.