feat(issue): Add automation for issue handling

[AkhileshNegi]

Issue

N/A

Summary

• Introduces a /fix-issue command for automating issue handling:
  • Pulls open issues labelled ready-for-agent based on priority.
  • Branches off main, implements, and opens a PR.
• Creates ready-for-agent label for issue queuing.
• Encodes repo-specific workflow:
  • Branches follow <type>/<kebab-slug> naming from issue labels.
  • Uses conventional commits for versioning.
  • Enforces linting and build checks.
• Usage:
  • /fix-issue for auto-pick from the queue.
  • /fix-issue 42 for a specific issue.

Checklist

Before submitting a pull request, please ensure that you mark these task.

• Ran npm run dev and npm run build in the repository root and test.
• If you've fixed a bug or added code that is tested

Original PR description

Issue

No tracking issue — infrastructure for how we pick up issues from here on.

Summary

We label issues by hand and then re-explain the same repo conventions to Claude Code every time someone picks one up — branch naming, which commit types semantic-release understands, which PR template headings to fill. That context gets rebuilt from scratch each session, and it drifts.

This adds a /fix-issue slash command that encodes the workflow once:

• .claude/commands/fix-issue.md — pulls open issues labelled ready-for-agent, picks one by priority (critical bugs → dev infra → tracer bullets → polish → refactors), branches off main, implements, and opens a PR.
• Created the ready-for-agent label on this repo so issues can be queued for pickup.
• Encodes repo-specific constraints rather than generic advice: <type>/<kebab-slug> branches mapped from the issue label, conventional commits (.releaserc drives versioning off them), npm run lint + npm run build as the gate, and .github/PULL_REQUEST_TEMPLATE.md headings used verbatim.

Usage: /fix-issue to auto-pick from the queue, or /fix-issue 42 for a specific one.

Checklist

Before submitting a pull request, please ensure that you mark these task.

• Ran npm run dev and npm run build in the repository root and test.
• If you've fixed a bug or added code that is tested

Notes

Docs-only change — no application code touched, so npm run dev / npm run build were not run and the checklist box is left unticked. lint-staged did run on commit (prettier reformatted the markdown).

Guardrails written into the command, worth a look since they're the safety story: branch + PR only, never push to main or merge (cd-dev.yml / deploy-staging.yml deploy from here), one issue per run, and stop-and-ask rather than guess when an issue touches auth, middleware gating, or the BFF contract.

Deliberately kept to two artifacts — the command file and the label. No workflow YAML, no scripts/ entry, no npm script; the command file is the automation. /pr-review stays the reviewing counterpart and is referenced rather than duplicated.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• ready-for-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: f0198ad4-c7cb-4aa9-8a7b-82e2454d2b7b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}