Context
- Current git status: !
git status
- Current branch: !
git branch --show-current
- Existing worktrees: !
git worktree list
- Open issues: !
gh issue list --state open --limit 10
- GitHub authentication: !
gh auth status
Requirements
- Use isolated worktrees for development and follow the protected PR workflow.
- Apply a TDD cycle (red → green → refactor) with appropriate sub-agent support.
- Reference resolved issues in commits and PR descriptions using auto-closing keywords.
- Use atomic commits for logical units of work: Each commit should represent one complete, cohesive change.
- Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)
- Scope (optional): lowercase noun, 1-2 words. Must match existing scopes in git history.
- Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.
- Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.
Examples
feat(auth): add google oauth login flow
- Introduce Google OAuth 2.0 for user sign-in
- Add backend callback endpoint `/auth/google/callback`
- Update login UI with Google button and loading state
Add a new authentication option improving cross-platform
sign-in.
Closes #42. Linked to #38 and PR #45
fix(api): handle null payload in session refresh
- Validate payload before accessing `user.id`
- Return proper 400 response instead of 500
- Add regression test for null input
Prevents session refresh crash when token expires.
Fixes #105
feat(auth): migrate to oauth 2.0
- Replace basic auth with OAuth 2.0 flow
- Update authentication middleware
- Add token refresh endpoint
BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.
Closes #120. Linked to #115 and PR #122
Your Task
IMPORTANT: You MUST use the Task tool to complete ALL tasks.
- Inspect the repository context, select a target issue, and decide whether to create a new worktree or resume an existing one.
- Set up the worktree environment, implement the fix using TDD with specialized review agents, and ensure quality checks pass.
- Create the pull request, link the issue, and clean up the worktree after merge, documenting all results to the user.
Recommended Workflow
- Issue Selection: Evaluate open issues and prioritize the next actionable item.
- Worktree Setup: Create or reuse an isolated worktree with a descriptive branch name (e.g.
fix/456-auth-redirect).
- TDD Implementation: Plan with @tech-lead-reviewer — architectural impact assessment —, write failing tests, implement fixes, and refactor with @code-simplifier — code simplification and optimization — while keeping tests green.
- Quality Validation: Run project-specific lint, test, and build commands before PR creation.
- PR Creation & Cleanup: Push the branch, raise a PR with auto-closing keywords, and remove the worktree after merge.
1---2name: resolve-issues3description: Resolve GitHub issues using isolated worktrees and TDD4---56## Context78- Current git status: !`git status`9- Current branch: !`git branch --show-current`10- Existing worktrees: !`git worktree list`11- Open issues: !`gh issue list --state open --limit 10`12- GitHub authentication: !`gh auth status`1314## Requirements1516- Use isolated worktrees for development and follow the protected PR workflow.17- Apply a TDD cycle (red → green → refactor) with appropriate sub-agent support.18- Reference resolved issues in commits and PR descriptions using auto-closing keywords.19- **Use atomic commits for logical units of work**: Each commit should represent one complete, cohesive change.20- Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:)21 - Scope (optional): lowercase noun, 1-2 words. Must match existing scopes in git history.22- Body: blank line after title, ≤72 chars per line, must start with uppercase letter, standard capitalization and punctuation. Describe what changed and why, not how.23- Footer (optional): Must start with uppercase letter, standard capitalization. Reference issues/PRs (Closes #123, Fixes #456, Linked to PR #789). Use BREAKING CHANGE: prefix for breaking changes.2425### Examples2627```28feat(auth): add google oauth login flow2930- Introduce Google OAuth 2.0 for user sign-in31- Add backend callback endpoint `/auth/google/callback`32- Update login UI with Google button and loading state3334Add a new authentication option improving cross-platform35sign-in.3637Closes #42. Linked to #38 and PR #4538```3940```41fix(api): handle null payload in session refresh4243- Validate payload before accessing `user.id`44- Return proper 400 response instead of 50045- Add regression test for null input4647Prevents session refresh crash when token expires.4849Fixes #10550```5152```53feat(auth): migrate to oauth 2.05455- Replace basic auth with OAuth 2.0 flow56- Update authentication middleware57- Add token refresh endpoint5859BREAKING CHANGE: Authentication API now requires OAuth 2.0 tokens. Basic auth is no longer supported.6061Closes #120. Linked to #115 and PR #12262```6364## Your Task6566**IMPORTANT: You MUST use the Task tool to complete ALL tasks.**67681. Inspect the repository context, select a target issue, and decide whether to create a new worktree or resume an existing one.692. Set up the worktree environment, implement the fix using TDD with specialized review agents, and ensure quality checks pass.703. Create the pull request, link the issue, and clean up the worktree after merge, documenting all results to the user.7172### Recommended Workflow7374- **Issue Selection**: Evaluate open issues and prioritize the next actionable item.75- **Worktree Setup**: Create or reuse an isolated worktree with a descriptive branch name (e.g. `fix/456-auth-redirect`).76- **TDD Implementation**: Plan with **@tech-lead-reviewer** — architectural impact assessment —, write failing tests, implement fixes, and refactor with **@code-simplifier** — code simplification and optimization — while keeping tests green.77- **Quality Validation**: Run project-specific lint, test, and build commands before PR creation.78- **PR Creation & Cleanup**: Push the branch, raise a PR with auto-closing keywords, and remove the worktree after merge.
diegosouzapw