// 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.
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.
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.
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 | prepare-mr |
| description | 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. |
| disable-model-invocation | true |
| invocable | manual |
Stage, commit, push, and generate an MR description. This skill has side effects — only run when the user explicitly asks.
Run in parallel:
git status — see all modified and untracked files.git diff — see unstaged changes only. Use git diff --staged (or git diff --cached) for staged changes, or git diff HEAD for all changes relative to the last commit.git log --oneline -10 — check recent commit style.Confirm with the user which files to include.
git add <files>
Exclude files that likely contain secrets (.env, credentials.json, etc.). Warn the user if they ask to include such files.
Use a concise commit message that follows the repo's existing style. Focus on the "why" not the "what".
git commit -m "<message>"
git push -u origin HEAD
Use this format:
## Summary
- <1-3 bullet points describing the change>
## Changes
- <bullet per file/area changed>
## Test Plan
- [ ] <specific test or verification step>
- [ ] <specific test or verification step>
## Cross-Language Impact
<if applicable — which layers were affected and how sync was maintained>
glab mr create --title "<title>" --description "<description>"
Present the MR URL to the user.