Find the perfect capability for your agent.
Reviews the git changes, identifies critical and high-priority issues, generates review summaries, and collects metrics data for local use. Use this when users need to code review or analyzing code changes for quality issues.
Monitor GitHub Actions workflow runs using blocking watch commands instead of polling with timeouts.
Convenience wrapper for listing Terraform Cloud runs in Forum Virium Helsinki workspaces (github, sentry, gcp, onelogin, twingate). Requires TFE_TOKEN. Use when user mentions TFC runs, Terraform Cloud workspace, listing TFC runs, infrastructure run history, or checking Terraform Cloud status.
Complete organization onboarding wizard for LimaCharlie. Discovers local cloud CLIs (GCP, AWS, Azure, DigitalOcean), surveys cloud projects, identifies VMs for EDR installation and security-relevant log sources (IAM, audit logs, network logs). Guides EDR deployment via OS Config (GCP), SSM (AWS), VM Run Command (Azure). Creates cloud adapters for log ingestion. Confirms sensor connectivity and data flow. Use when setting up new tenants, connecting cloud infrastructure, deploying EDR fleet-wide, or onboarding hybrid environments.
Senior DevOps Engineer with 12+ years cloud infrastructure experience. Use when setting up cloud infrastructure, writing Terraform configurations, creating Kubernetes manifests, building CI/CD pipelines with GitHub Actions, configuring Docker, or managing secrets.
Generate clear, conventional, and meaningful commit messages following best practices and conventional commit standards
Enforces conventional commit message and branch naming conventions with specific prefixes (feat, fix, docs, style, refactor, perf, test, chore). Use when creating git commits, suggesting branch names, reviewing commit messages, or when the user asks about git workflow.
Automatically detect GitHub issues that staged changes may fix or close. Analyzes diffs, file paths, and issue metadata to suggest appropriate closing keywords (Fixes, Closes, Resolves) for commit messages. Use when committing changes to ensure proper issue linkage.
Commit message conventions, staging practices, and commit best practices. Covers conventional commits, explicit staging workflow, logical change grouping, humble fact-based communication style, and automatic issue detection. Use when user mentions committing changes, writing commit messages, git add, git commit, staging files, or conventional commit format.
Protect repositories from accidental secret commits. Essential when working with AI agents. Use when: setting up new project, adding pre-commit hooks, scanning for secrets, fixing leaked credentials. Triggers: "настрой защиту секретов", "setup secrets", "check secrets", "scan secrets", "проверь секреты", "pre-commit", "gitleaks". PROACTIVELY suggest when creating new projects or when .pre-commit-config.yaml is missing.
Isolated workspace creation for parallel development work. Use when starting feature work that needs isolation from the current workspace. Creates git worktrees with proper setup and safety verification.
Branch management, pull request workflows, and GitHub integration. Main-branch development pattern (push main to remote feature branches), modern Git commands (switch, restore), branch naming conventions, linear history, and GitHub MCP tools. Use when user mentions creating branches, opening PRs, git switch, git restore, feature branches, pull requests, or GitHub PR workflows.
Manages git operations: worktree creation, branch management, commits, PRs, semantic versioning, daily rebase workflow, and PR feedback handling. Use when: Creating branches/worktrees, committing, pushing, versioning, handling PR feedback Triggers: create worktree, commit, push, rebase, version, PR, PR feedback
MUST use when committing changes to a git repository, contains guidelines for creating git commit messages
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (<<<<<<< =======), or need help resolving conflicted files
