Hugo Nijhuis
cdfacbac18
- Move legacy content to legacy/ folder (old, old2, docs, learnings, scripts) - Create new .opencode/ structure with skills/, tools/, agents/ folders - Update Makefile to symlink to ~/.config/opencode/ instead of ~/.claude/ - Update Makefile to manage skills, tools, and agents (remove settings.json) - Simplify install/uninstall (no backup logic) - Add README.md documenting the new structure - Keep settings.json as historical reference
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
---
|
|
name: work-issue
|
|
description: >
|
|
Work on a Gitea issue. Fetches issue details and sets up branch for implementation.
|
|
Use when working on issues, implementing features, or when user says /work-issue.
|
|
model: haiku
|
|
argument-hint: <issue-number>
|
|
user-invocable: true
|
|
---
|
|
|
|
# Work on Issue #$1
|
|
|
|
@~/.claude/skills/gitea/SKILL.md
|
|
@~/.claude/skills/software-architecture/SKILL.md
|
|
|
|
1. **View the issue** with `--comments` flag to understand requirements and context
|
|
2. **Create a branch**: `git checkout -b issue-$1-<short-kebab-title>`
|
|
3. **Plan**: Use TodoWrite to break down the work based on acceptance criteria
|
|
4. **Check architecture**: Review the project's vision.md Architecture section for project-specific patterns and divergences
|
|
5. **Implement** the changes following architectural patterns (DDD, event sourcing where appropriate)
|
|
6. **Commit** with message referencing the issue
|
|
7. **Push** the branch to origin
|
|
8. **Create PR** with title "[Issue #$1] <title>" and body "Closes #$1"
|
|
9. **Auto-review**: Inform the user that auto-review is starting, then spawn the `code-reviewer` agent in background (using `run_in_background: true`) with the PR number
|