- Add LLM_SERVICES variable for easy service management
- Add restart-llm-% pattern rule for individual service control
- Refactor restart-llm to loop through services
- Use full model names (claude-haiku-4-5, etc.) in create-capability
- Add allowed-tools to gitea skill for tea/jq commands
- Set default model to opus in settings
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- tea issues output has title on line 2, not line 1
- Update sed command to extract from correct line
- Fixes branches being named "issue-N-" or "issue-N-untitled"
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add step 5 to merge approved PRs using tea pulls merge --style rebase
- Clean up branch after merge with tea pulls clean
- Update role description and outputs to reflect merge responsibility
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Added explicit instructions to keep PR comments extremely brief:
- Maximum 3-4 bullet points
- One line per bullet
- Just state what was fixed
- No verbose explanations
- No code snippets
- No apologizing or thanking
Before: Long, verbose comments explaining every change in detail
After: "Fixed review feedback ✓
- Fixed error handling
- Added null checks
- Updated tests"
Updated:
- Added step 6: Post Concise Comment
- Added format examples (good vs bad)
- Added "Keep comments concise" to Guidelines
- Updated description and Your Role section
- Emphasized in Tips section
Co-Authored-By: Claude Code <noreply@anthropic.com>
Creates new user-invocable skill for fixing PRs based on review feedback:
- Takes multiple PR numbers as arguments
- Creates isolated fix worktrees for each PR
- Spawns pr-fixer agents in parallel
- Event-driven result handling
- Addresses review comments autonomously
- Commits and pushes fixes to Gitea using tea
- Shows detailed summary of all fixes
Uses tea and gitea skill (not gh). Pattern matches spawn-issues and
spawn-pr-reviews: Haiku orchestrator with allowed-tools.
Completes the spawn trilogy:
- spawn-issues: full workflow (implement → review → fix)
- spawn-pr-reviews: review only (read-only)
- spawn-pr-fixers: fix only (based on feedback)
Co-Authored-By: Claude Code <noreply@anthropic.com>
Creates new user-invocable skill for reviewing PRs:
- Takes multiple PR numbers as arguments
- Creates isolated review worktrees for each PR
- Spawns code-reviewer agents in parallel
- Event-driven result handling
- Posts review comments to Gitea using tea
- Read-only operation (no auto-fixes)
Uses tea and gitea skill (not gh), avoiding conflicts with base
system instructions.
Pattern matches spawn-issues: Haiku orchestrator with allowed-tools
for bash execution.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Removed outdated skills that haven't been migrated from old/ directory:
- /manifesto, /vision, /work-issue, /dashboard, /review-pr
- /create-issue, /retro, /plan-issues, /groom
Added current user-invocable skills:
- /vision-to-backlog
- /create-milestones
- /spawn-issues
- /create-capability
- /capability-writing
This prevents confusion when users try non-existent skills, which could
cause the system to fall back to base instructions (using gh instead of tea).
Co-Authored-By: Claude Code <noreply@anthropic.com>
The spawn-issues skill was missing the allowed-tools field that was present
in the old version. Without this field, the skill cannot execute bash commands,
causing permission errors when trying to create worktrees or call scripts.
Added: allowed-tools: Bash, Task, Read, TaskOutput
Co-Authored-By: Claude Code <noreply@anthropic.com>
Users were confused by ./scripts/ references, thinking they needed to copy
scripts into their project. Scripts are in ~/.claude/skills/worktrees/scripts/
and should be referenced with full paths.
Changes:
- Updated spawn-issues to use full script paths
- Updated worktrees skill with full paths in all examples
- Fixed gitea model name to claude-haiku-4-5
- Added tools list to issue-worker agent
Co-Authored-By: Claude Code <noreply@anthropic.com>
Restructure steps 7-8 to be clearer and more efficient:
- Merged "Assign Issues" and "Apply Labels" into single step
- Explicit nested loop structure: milestone → issues in that milestone
- Process one milestone at a time
- Combine milestone assignment + labels in single tea command
- Added clear examples
- Prevents confusion about looping and when to move on
Before: Separate loops for milestone assignment and label application
After: Single pass through milestones, process all issues per milestone
Co-Authored-By: Claude Code <noreply@anthropic.com>
Clarify that after user approves issues at decision gate, workflow should
automatically proceed to create all issues in Gitea without waiting for
another prompt.
Changes:
- Step 13: Clear yes/no question "Ready to create these issues in Gitea?"
- Step 14: Marked as "automatic after approval"
- Guidelines: Added "Automatic execution after approval" section with example
Prevents workflow from stopping and requiring user to explicitly request
issue creation after already approving the backlog.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Add capability for organizing backlog into shippable business capabilities
using value-based milestones (not time-based phases).
Components:
- milestone-planning skill: Value-based framework, vertical slice test, one active milestone
- create-milestones skill: Orchestrator (Haiku) for analyzing and grouping issues
- milestone-planner agent: Groups issues into capabilities autonomously (Haiku)
Core Principles:
- Milestone = shippable business capability (not phase)
- One active milestone at a time (preserves focus)
- 5-25 issues per milestone (right-sized)
- Value labels: value/high, value/medium, value/low
- Risk labels: risk/high (optional)
- Vertical slice test (can be demoed independently)
- No dates (capability-based, not time-based)
Workflow: /create-milestones reads existing Gitea issues → analyzes capability
boundaries → groups into milestones → creates in Gitea → assigns issues →
applies labels → user manually activates ONE milestone
Co-Authored-By: Claude Code <noreply@anthropic.com>
Split gitea skill into main file and reference documentation.
Main SKILL.md now focuses on core commands (154 lines, down from 201),
with setup/auth and CI/Actions moved to reference files.
Co-Authored-By: Claude Code <noreply@anthropic.com>
Remove top-level model override to allow per-skill/agent model configuration.
Reorder sections for consistency.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Claude Code has unified commands into skills with the user-invocable
frontmatter field. This migration:
- Converts 20 commands to skills with user-invocable: true
- Consolidates docs into single writing-capabilities.md
- Rewrites capability-writing skill for unified model
- Updates CLAUDE.md, Makefile, and other references
- Removes commands/ directory
Skills now have two types:
- user-invocable: true - workflows users trigger with /name
- user-invocable: false - background knowledge auto-loaded
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
