coreyhaines31/makerskills / skills/castmate
castmate
FlaggedWhen you want to pull in the right AI model for the right job: hand a task to another agent CLI (Codex, Claude, Gemini, Grok, Amp, OpenCode, Cursor, Kiro, Antigravity), or send one prompt to several at once for independent opinions, then synthesize. Delegate mode gives one castmate the job, optionally with write access ('have codex write the migration'). Fan-out mode runs read-only reviews in parallel. Rounds mode lets castmates build on and challenge each other's findings. Calls the official CLIs you already have installed and logged in (Gemini CLI needs an API key on personal accounts); no MCP. Triggers on '/castmate,' 'ask codex,' 'have gemini do this,' 'get a second opinion,' 'what would other models say,' 'fan this out,' 'cross-check this with another model,' 'delegate this to codex.' Advisor personas for founder questions go to maker-council. Personal models, casting rules, and run outputs live in ~/.config/makerskills/castmate/.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.7 KB |
| references/amp-readonly-settings.json | config | 229 B |
| references/casting.md | markdown | 2.6 KB |
| references/cli-setup.md | markdown | 11.3 KB |
| references/gemini-readonly-policy.toml | config | 857 B |
| references/presets/README.md | markdown | 757 B |
| references/presets/bughunt.md | markdown | 1.6 KB |
| references/presets/contracts.md | markdown | 1.1 KB |
| references/presets/hotspots.md | markdown | 1.7 KB |
| references/presets/invariants.md | markdown | 1.5 KB |
| references/presets/regression.md | markdown | 1.1 KB |
| references/presets/security.md | markdown | 1.5 KB |
| references/prompt-template.md | markdown | 3.1 KB |
| references/tools.json | config | 9.1 KB |
| scripts/castmate.pyexecutable | script | 21.1 KB |
| scripts/test_castmate.py | script | 11.7 KB |
references/presets/bughunt.md
View on GitHub# bughunt
Default rounds: 3. Read-only.
You are hunting for real correctness bugs, edge-case failures, and missing tests that would allow regressions.
Prioritize:
- User-visible correctness failures over style issues
- High-blast-radius bugs over speculative nits
- Findings likely to produce meaningful failing tests
Look for:
- Logic errors: wrong conditionals, off-by-one, incorrect defaults, null/undefined handling gaps
- Boundary and error-path failures: empty inputs, max/min values, partial failures, cleanup/rollback gaps
- Validation and contract gaps: unchecked inputs, missing type guards, mismatched return assumptions
- Concurrency/order bugs: TOCTOU, race conditions, shared mutable state hazards, invalid async state transitions
- Resource-lifecycle bugs: unclosed handles, unreleased locks, dangling listeners, swallowed exceptions in finally blocks
- Missing test coverage on risky branches: error handlers, retry logic, fallback paths, migration paths
Multi-round rule:
- Prioritize novel findings not already reported in prior rounds.
- If you repeat a prior finding, add new evidence, sharper impact analysis, or a better test strategy.
For each finding, include:
- severity: critical | high | medium | low
- confidence: high | medium | low
- location: file path + function/method name
- evidence: concrete code pattern and why it can fail at runtime
- impact: user/system consequence if triggered
- minimal fix: smallest safe change
- test idea: a concrete failing test scenario (inputs + expected behavior)
Skip trivial style comments unless they hide a correctness bug.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |