User-started triage of local git branches and worktrees: sorts each into delete, needs review or keep from git state and merge or squash commit messages (gh optional), tries to disprove every delete candidate, and removes nothing until the user picks branches at a first gate and approves the exact commands at a second. Never touches remotes or pull requests.
Plugin git-cleanup from marketplace devops in flyoverhead/devops-plugins. Commands read from the repo's manifest — today.
git-cleanupSorts the local branches and worktrees of one git repository into delete, needs review and keep, backing each deletion with ancestry, merge or squash commit messages, optional `gh pr list` or a superseding branch, tries to disprove it, and deletes only after two answers — which branches, then yes to
branch-investigatorLooks for proof that each branch in one batch from git-cleanup:git-cleanup is already squash-merged or superseded, then tries to knock that proof down, and returns one record per branch. Inspects git only; deletes nothing. Dispatched by that skill for large batches, not for direct use.
Go toolkit: version-aware idioms, concurrency fixes proven with the race detector, performance work backed by benchmarks and profiles, read-only code review, tests that match the repository, a GitHub-ready project scaffold and gopls LSP.
5 skills · 3 agents · hooks · LSP
Did a PR, commit or commit range break something that used to work? Pins the before and after states, hunts candidate regressions in the diff, then has three separate fresh agents reproduce, replay and adjudicate each one on live S0 and S1 builds. Sealed evidence, an attempt registry and an HTML/Markdown/JSON report stay in a campaign directory outside the repo; GitHub is only read.
7 skills
Ansible toolkit: role creator in the classic upstream layout (install/configure/service, meta/argument_specs.yml, sentence-case names, true/false, FQCN, ansible-lint production profile), role checker and molecule scaffolder, plus a guard on real ansible-playbook runs
3 skills · 1 agent · hooks
One reported bug, reproduced on the unchanged build, re-run blind by a second agent, fixed at its invariant with a failing-first regression test and a single signed-off local commit, then proven on baseline, patched and reverted worktrees by yet another agent. Records, receipts and hash manifests stay in $TMPDIR; nothing is pushed.
5 skills
Terraform toolkit: module-creator for YAML-driven modules with inheritance and validation layers (OpenStack, VMware, AWS, Azure, GCP, Proxmox), provider-creator for Plugin Framework providers with a GitHub Actions release, plus terraform-ls LSP and safety hooks
2 skills · 1 agent · hooks · LSP
Settles whether suspected security findings tied to a code location are real: restates each claim, traces source to sink, proves or refutes attacker control and impact, writes PoCs outside the repo without running them, and passes six gates before a TRUE or FALSE POSITIVE verdict. Takes scanner output, review findings or a pasted GitHub code-scanning alert.
1 skill · 3 agents
Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
200 skills · 98 commands · 71 agents · 1 MCP server · hooks
Commands for git commit workflows including commit, push, and PR creation
3 commands
Agent teams, swarm coordination, Monitor streams, and worktree isolation
2 skills · 2 commands · 2 agents
Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.
2 commands
Install the "AAS Security Engineer" editorial skill bundle for Claude Code.
12 skills
Duende development skills and agents for Claude Code — covering OAuth/OIDC protocols, IdentityServer, token management, ASP.NET Core authentication/authorization, BFF patterns, and secure identity architecture
24 skills · 2 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.