github-ops

Label-driven loops that take an issue from rough idea to merged PR: `ai-discussing` talks it into shape before anyone builds it, `ai-ready` builds it to a PR, `auto-reworking` acts on your review feedback. Bundles issue-discuss-loop, issue-build-loop, rework-loop, and mcp-review. Fired by the agent-orchestration Worker as a cloud routine. Repo-agnostic.

5 skills · 2 agents

Branching, merge, release, and dev-sync workflow skills for any repo — detects gitflow (dev + main) vs main-only and follows the matching conventions. Bundles release-and-branching, sync-dev, and auto-release-loop (issue+label-triggered release with two automated gates — green CI + an Opus pre-publish review against a growing checklist — no approval pause).

4 skills · 1 agent

Iteratively trims a Claude Code skill (SKILL.md + its bundled resources) down to exactly what it needs — repeated review/fix rounds against a concrete duplication-and-bloat checklist, with a fresh independent reviewer each round, until two consecutive rounds find nothing left to change (or a hard cap is hit and reported as non-convergence, never silently accepted). Bundles the skill-tighten skill and its read-only skill-tightener-reviewer agent.

1 skill · 3 agents

Shared skill for writing the structured outcome artifact a loop appends to a comment it already posts, so the agent-orchestration Worker can read what happened and apply the labels itself. One marker format, one growing catalog of outcome shapes; loop plugins point here instead of each inventing their own. Loops report through post-outcome.sh, which signals the agent-orchestration Worker and prints the exact comment body to post. Bundles hooks that signal it too: heartbeats naming the step while a loop works, blocked on a permission prompt, and ended when a session stops without reporting (AGENT_OUTCOMES_ENDPOINT + AGENT_OUTCOMES_TOKEN; without the endpoint they send nothing). Also bundles the work-log skill: how a loop records its decisions and what it verified in the Worker's decision log and build log, with log-entry.sh to add and read entries.

2 skills · hooks

Single front door for a repo's automation loops so one routine per repo can handle every loop event instead of one routine per event. Deterministically routes each triggering GitHub event to the matching loop (via route-event.sh); a non-matching event is a quiet no-op. Router only; each loop owns its guardrails. Also bundles new-loop-routine — the standard config + canonical prompts + UI wiring for standing up one routine per repo. Requires github-ops + the loop skills.

3 skills

The self-learning system shared by every automated loop in this repo. SubagentStop/SessionEnd hooks capture proto-learnings — raw observations worth improving — as rows on a shared Slack canvas (not GitHub issues, which silently lose captures across an org boundary). The hooks fire for any loop, matching on shared conventions (github-ops, /goal) rather than naming individual loops, so a new loop needs no integration here. Bundles two separate skills: proto-learning-capture (reference for the capture half and its row schema) and triage-learnings (Loop B), which weekly dedupes/clusters the canvas inbox and routes each cluster to a tracked issue on the owning MCP repo, a gated PR to the shared umbraco-mcp-skills, or a loop-improvement issue on this repo. Install alongside any loop plugin to get capture for free.

2 skills · hooks

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

Repomix MCP server for AI-powered codebase analysis. Pack local/remote repositories and search or read the generated outputs. Foundation plugin that enables all Repomix features in Claude Code.

1 MCP server

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

Architecture diagrams, explanations and Mermaid source for any public GitHub repository, from gitdiagram.com.

2 skills · 1 MCP server

Connect Claude to Prowler Cloud through the Prowler MCP server. Reads providers, scans, findings, compliance results and resources for AWS, Azure, GCP, Kubernetes, Microsoft 365, GitHub and the other providers listed at https://registry.prowler.com, and returns remediation guidance for failed checks. Writes are limited to Prowler Cloud itself: triggering scans, finding triage, mute rules and the mutelist, providers and integrations. Your cloud resources are not changed by the connector.

1 skill · 1 MCP server