feat(reusable): ship the curated swarm as the default config consumers inherit
Make the reusable workflow's input defaults BE the standard Gadfly swarm so a consumer subscribes by just calling it (no `with:` block) and inherits: - models: 3 strong cloud (minimax-m3, glm-5.2, deepseek-v4-pro) + Claude Code (sonnet, opus, opus:max) - specialists: the 5-lens default suite (security, correctness, maintainability, performance, error-handling) - provider_concurrency: ollama-cloud=3,claude-code=3 (all three claudes at once) - timeout_minutes default 45 -> 90 (5 lenses x 2 passes over a slow lane) The default is opinionated (needs OLLAMA_CLOUD_API_KEY + CLAUDE_CODE_OAUTH_TOKEN); consumers override `models:` for cloud-only / other providers. gadfly's own caller is slimmed to inherit (only allowed_users remains). examples/reusable.yml keeps a cloud-only `models:` override so a public copy works with just the Ollama key. README/CLAUDE.md updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -39,7 +39,8 @@ it. Drop one file in your repo and set a couple of secrets/vars:
|
||||
1. Copy a stub from [`examples/`](examples/) to `.gitea/workflows/adversarial-review.yml` in
|
||||
your repo. Two flavors: the slim [`reusable.yml`](examples/reusable.yml) — a tiny caller of
|
||||
Gadfly's **reusable workflow** (`uses: steve/gadfly/.gitea/workflows/review-reusable.yml@…`,
|
||||
forwarding only the secrets the reviewer needs), best when you take the defaults — or the full self-contained
|
||||
forwarding only the secrets the reviewer needs), which ships a **default swarm** (3 cloud models +
|
||||
the Claude Code engine, 5-lens suite) you inherit by omitting `with:` or override per-input — or the full self-contained
|
||||
[`adversarial-review.yml`](examples/adversarial-review.yml) (Ollama Cloud default, with inline
|
||||
notes for every provider / local Ollama / OpenAI-compatible / endpoint aliases). See the
|
||||
[examples index](examples/README.md).
|
||||
|
||||
Reference in New Issue
Block a user