docs: update branch naming convention from issue/ to feat/ (#44)

[tetsuh]

Closes #44

Changes

• docs/development_workflow.md §1: branch name rule changed from issue/<number>-... to feat/<number>-...
• AGENTS.md: absolute rules summary updated accordingly

Verification

git grep "issue/<" -- docs/ AGENTS.md
# no output

Scope note

docs/07_issue_breakdown.md does not contain branch-name examples, so no changes were needed there.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ec1684c8-aa1e-49a5-bff3-64e8ffb140de

📥 Commits

Reviewing files that changed from the base of the PR and between 6fb8f99 and 96a71d1.

📒 Files selected for processing (2)

• AGENTS.md
• docs/development_workflow.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Updated branching examples to use a feat/<number>-<short-kebab-description> format.
  • Kept the existing PR closing reference format unchanged.
  • Aligned workflow guidance with the new branch naming convention.

Walkthrough

Two documentation files were updated to change the branch naming convention example from issue/<n>-<short-kebab-description> to feat/<n>-<short-kebab-description>, affecting AGENTS.md and docs/development_workflow.md.

Changes

Branch naming convention update

Layer / File(s)	Summary
Branch naming examples updated AGENTS.md, docs/development_workflow.md	Branch name format examples changed from issue/<n>-... to feat/<n>-... in both the AI agent rules and the trunk-based workflow documentation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Related issues: #44 (docs: update branch naming convention from issue/ to feat/)

Suggested labels: documentation

Suggested reviewers: tetsuh

🐰 Poem

A rabbit hops through docs anew,
Swapping "issue" for "feat" on cue,
One small word, a tidy trace,
Branch names now in proper place,
Hop hop, convention passes through! 🐇

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/44-update-branch-naming-convention

---

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.}