Some checks failed
PR Checklist / pr-checklist (pull_request) Failing after 1m18s
Golden state: Kimi K2.5 primary → Gemini via OpenRouter → local Ollama. Anthropic is gone from every active config, fallback chain, and loop script. Wizard configs (3): - allegro, bezalel, ezra: removed anthropic from fallback_providers, replaced with gemini + ollama. Removed anthropic provider section. Playbooks (7): - All playbooks now use kimi-k2.5 as preferred, google/gemini-2.5-pro as fallback. No claude model references remain. Fleet scripts (8): - claude-loop.sh: deprecated (exit 0, original preserved as reference) - claudemax-watchdog.sh: deprecated (exit 0) - agent-loop.sh: removed claude dispatch case - start-loops.sh: removed claude-locks, claude-loop from proc list - timmy-orchestrator.sh: removed claude worker monitoring - fleet-status.sh: zeroed claude loop counter - model-health-check.sh: replaced check_anthropic_model with check_kimi_model - ops-gitea.sh, ops-helpers.sh, ops-panel.sh: removed claude from agent lists Infrastructure (5): - wizard_bootstrap.py: removed anthropic pip package and API key checks - WIZARD_ENVIRONMENT_CONTRACT.md: replaced ANTHROPIC keys with KIMI - DEPLOY.md: replaced ANTHROPIC_API_KEY with KIMI_API_KEY - fallback-portfolios.yaml: replaced anthropic provider with kimi-coding - fleet-vocabulary.md: updated Ezra and Claude entries to Kimi K2.5 Docs (2): - sonnet-workforce.md: deprecated with notice - GoldenRockachopa-checkin.md: updated model references Preserved (not touched): - training/ data (changing would corrupt training set) - evaluations/ (historical benchmarks) - RELEASE_*.md (changelogs) - metrics_helpers.py (historical cost calculation) - hermes-sovereign/githooks/pre-commit.py (secret detection - still useful) - security/secret-scan.yml (key detection - still useful) - architecture_linter.py (warns about anthropic usage - desired behavior) - test_sovereignty_enforcement.py (tests anthropic is blocked - correct) - son-of-timmy.md philosophical references (Claude as one of many backends) Refs: Sovereignty directive, zero-cloud vision
76 lines
1.8 KiB
YAML
76 lines
1.8 KiB
YAML
name: refactor-specialist
|
|
description: 'Splits large modules, reduces complexity, improves code organization. Well-scoped: 1-3 files per task, clear
|
|
acceptance criteria.
|
|
|
|
'
|
|
model:
|
|
preferred: kimi-k2.5
|
|
fallback: google/gemini-2.5-pro
|
|
max_turns: 30
|
|
temperature: 0.3
|
|
tools:
|
|
- terminal
|
|
- file
|
|
- search_files
|
|
- patch
|
|
trigger:
|
|
issue_label: refactor
|
|
manual: true
|
|
repos:
|
|
- Timmy_Foundation/the-nexus
|
|
- Timmy_Foundation/timmy-home
|
|
- Timmy_Foundation/timmy-config
|
|
- Timmy_Foundation/hermes-agent
|
|
steps:
|
|
- read_issue
|
|
- clone_repo
|
|
- create_branch
|
|
- dispatch_agent
|
|
- run_tests
|
|
- create_pr
|
|
- comment_on_issue
|
|
output: pull_request
|
|
timeout_minutes: 15
|
|
system_prompt: 'You are a refactoring specialist for the {{repo}} project.
|
|
|
|
|
|
YOUR ISSUE: #{{issue_number}} — {{issue_title}}
|
|
|
|
|
|
RULES:
|
|
|
|
- Lines of code is a liability. Delete as much as you create.
|
|
|
|
- All changes go through PRs. No direct pushes to main.
|
|
|
|
- Use the repo''s own format, lint, and test commands rather than assuming tox.
|
|
|
|
- Every refactor must preserve behavior and explain how that was verified.
|
|
|
|
- If the change crosses repo boundaries, model-routing, deployment, or identity surfaces, stop and ask for narrower scope.
|
|
|
|
- Never use --no-verify on git commands.
|
|
|
|
- Conventional commits: refactor: <description> (#{{issue_number}})
|
|
|
|
- If tests fail after 2 attempts, STOP and comment on the issue.
|
|
|
|
- Refactors exist to simplify the system, not to create a new design detour.
|
|
|
|
|
|
WORKFLOW:
|
|
|
|
1. Read the issue body for specific file paths and instructions
|
|
|
|
2. Understand the current code structure
|
|
|
|
3. Name the simplification goal before changing code
|
|
|
|
4. Make the refactoring changes
|
|
|
|
5. Run formatting and verification with repo-native commands
|
|
|
|
6. Commit, push, create PR with before/after risk summary
|
|
|
|
'
|