Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue (Stripe+RevenueCat), e-commerce (Shopify), marketing (Klaviyo/Meta/GA4), voice (Bland/ElevenLabs), APM (Datadog/NewRelic/OTEL), YOLO mode.
Contributing to claude-ops
PRs welcome from anyone. This document covers the branch strategy, protection rules, and PR workflow.
Branch Strategy
mainis the only long-lived branch and the default branch.- All work happens on feature branches (e.g.,
fix/setup-gog-url,feat/stripe-revenue). - Feature branches are merged into
mainvia PR. - There is no
devbranch.
Branch Protection
main is protected by three layers of rulesets (repo-level + org-level):
| Rule | Maintainer | External contributors |
|---|---|---|
| Direct push | Allowed | Blocked |
| Force push | Blocked | Blocked |
| Delete branch | Blocked | Blocked |
| Merge PR without approval | Allowed | Requires 1 approval |
| Unresolved review threads | Allowed | Blocked |
These rules are enforced at both the repository and organization level and cannot be overridden by repository settings alone.
PR Workflow
For external contributors
- Fork the repo
- Create a feature branch from
main - Make your changes
- Open a PR targeting
main - Wait for review and approval from a maintainer
- Once approved, a maintainer will merge your PR
For maintainers
- Create a feature branch from
main - Push the branch and open a PR targeting
main - Resolve any automated review comments (Copilot code review runs on push)
- Merge via
gh pr merge --merge --admin
Local Development
# Clone and run in development mode
git clone https://github.com/Lifecycle-Innovations-Limited/claude-ops.git
cd claude-ops
claude --plugin-dir ./claude-ops/claude-ops
# After making changes, reload without restarting
/reload-plugins
Code Review
- Copilot code review runs automatically on every push and may leave review threads.
- All review threads must be resolved before merge (for non-maintainers).
- Maintainers can resolve threads and merge without external approval.
License
By contributing, you agree that your contributions will be licensed under the MIT License.
Adding a new agent adapter (installer)
The installer/ package ships per-agent adapters so a single npx claude-ops-installer install works across CLIs. To add support for a new CLI:
- Add an entry to
installer/src/detect.mjsAGENT_DEFSwith the CLI binary name + the expected skill path. - Add the same agent to
installer/src/config.mjsDEFAULT_CONFIG.agents(default off; let the operator opt in). - Smoke-test:
cd installer && npm test— the smoke test reads the source layout, plans, and applies; it covers all agent paths through the same code, so a new agent passes automatically as long asAGENT_DEFSand the config are consistent. - Update
installer/README.mdwith the new agent in the "Supported agents" table. - Update
CHANGELOG.mdunder## Unreleased→### Added.
The adapter is pure: it does not need an agents/<name>.mjs file unless the new CLI needs a non-flat layout. If it does, see installer/src/dispatch.mjs pickAgents and add the per-agent branch.