// Produce a test plan with specific test names, assertions, and coverage across Python, Rust, and Go. Use when planning tests for a feature, after generating a spec, or the user asks for a test plan.
Append a learning to agent-learnings.md when the agent or user identifies a mistake, non-obvious pattern, or useful convention worth remembering. Use when the user says "capture this", "remember this", or "add to learnings".
Set up MSC credentials and MCP server integration for cloud storage access. Use when the user wants to interact with cloud storage (S3, GCS, Azure, OCI), asks to set up credentials, connect to a bucket, list objects, move files, or sync data. Checks for existing config first — only runs interactive setup if credentials are missing.
Fix CVE vulnerabilities by upgrading affected dependencies across Python (uv), Go, and Rust layers. Use when the user mentions CVE numbers, asks to fix security vulnerabilities, or asks to patch dependencies for CVEs.
Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Stage files, commit with correct format, push, and generate an MR description. Manual invocation only — has side effects (git operations). Use when the user explicitly asks to prepare, create, or submit an MR.
Prepares and automates the release process for multi-storage-client (version bump, release notes, checklist). Use when the user wants to cut a release, bump version, prepare release, publish a new version, or automate release steps.
| name | generate-test-plan |
| description | Produce a test plan with specific test names, assertions, and coverage across Python, Rust, and Go. Use when planning tests for a feature, after generating a spec, or the user asks for a test plan. |
| invocable | auto |
Produce a concrete test plan with specific file paths, test names, and assertions. Covers all affected language layers.
From the feature spec (or user description), determine:
Use this template:
## Test Plan: <feature title>
### Python Unit Tests
File: `tests/test_multistorageclient/test_<module>.py`
| Test Name | What It Verifies |
|-----------|-----------------|
| `test_<name>` | <specific assertion> |
| `test_<name>` | <specific assertion> |
### Rust Tests (if applicable)
File: `rust/src/<module>.rs` (inline `#[cfg(test)]`)
| Test Name | What It Verifies |
|-----------|-----------------|
| `test_<name>` | <specific assertion> |
### Go Tests (if applicable)
File: `posix/fuse/mscp/<module>_test.go`
| Test Name | What It Verifies |
|-----------|-----------------|
| `Test<Name>` | <specific assertion> |
### Integration Tests (if applicable)
File: `tests/integration/test_<scenario>.py`
| Test Name | What It Verifies |
|-----------|-----------------|
| `test_<name>` | <specific assertion across providers/layers> |
### Edge Cases
- <edge case 1 and which test covers it>
- <edge case 2 and which test covers it>
### Run Commands
- Python: `just multi-storage-client/run-unit-tests`
- Rust: `cd multi-storage-client/rust && cargo test`
- Go: `cd multi-storage-file-system && go test ./...`
Present the test plan to the user. Adjust scope if needed before proceeding.