agentuity-cli-cloud-keyvalue-list-namespaces
List all keyvalue namespaces. Requires authentication. Use for Agentuity cloud platform operations
List all keyvalue namespaces. Requires authentication. Use for Agentuity cloud platform operations
Set a key and value in the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations
List all keyvalue namespaces. Requires authentication. Use for Agentuity cloud platform operations
Create a new keyvalue namespace. Requires authentication. Use for Agentuity cloud platform operations
Set a key and value in the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations
This rule book helps you migrate Bitnami Helm charts and container images from the bitnami repository to the bitnamilegacy repository. This migration is necessary due to Bitnami's transition, effective August 28th, 2025, where existing images will be moved to the legacy repo
Create a new keyvalue namespace. Requires authentication. Use for Agentuity cloud platform operations
Use when implementing features in git worktrees to ensure all changes stay in the correct worktree - prevents "bleeding" of changes back to main branch
MUST use this skill when user asks to check/review PR comments, address reviewer feedback, fix review issues, or respond to code review. Fetches unresolved review comments from GitHub PR for the current branch.
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with sisyphus_task(category='quick', skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
Generate conventional commit messages from staged changes. Runs autonomously using Haiku model. Use after completing TDD cycles, after refactoring sessions, or when ready to commit.
Use when you need a Conventional Commits message from staged git changes or a pasted diff - guides type/scope selection and subject/body/footer formatting for a compliant commit message
The model must use this skill when : 1. working within any python project. 2. Python CLI applications with Typer and Rich are mentioned by the user. 2. tasked with Python script writing or editing. 3. building CI scripts or tools. 4. Creating portable Python scripts with stdlib only. 5. planning out a python package design. 6. running any python script or test. 7. writing tests (unit, integration, e2e, validation) for a python script, package, or application. Reviewing Python code against best practices or for code smells. 8. The python command fails to run or errors, or the python3 command shows errors. 9. pre-commit or linting errors occur in python files. 10. Writing or editing python code in a git repository.\n<hint>This skill provides : 1. the users preferred workflow patterns for test-driven development, feature addition, refactoring, debugging, and code review using modern Python 3.11+ patterns (including PEP 723 inline metadata, native generics, and type-safe async processing). 2. References to favor
Provides Git workflow conventions. Use when the user asks to "create a commit", "make a branch", "open a PR", "push changes", "sync with main", "resolve merge conflicts", or when working with git operations, conventional commits, or version control workflows.
Reimplement the current Git branch on a fresh branch off `main` with a clean, narrative-quality commit history.
Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.
Use when starting new feature work to create isolated git worktrees with smart directory selection and safety verification. Keeps main branch clean while developing.