bear-notes-mcp

# When performing a code review for a PR

## Review Objective
- Perform the PR review as instructed in the "Review Guidelines" section below.
- Be specific, concise, and actionable in your feedback.
- Explain the "why" behind your recommendations.
Never assume — only state what you know for sure based on the new code you review and the existing codebase.

## Review Guidelines
1. Review for KISS and DRY
- Carefully read the docs/dev/SPECIFICATION.md file, which explains the system architecture and design constraints (including KISS/YAGNI principles) for this project.
- Using this knowledge, diligently review the PR changes according to these principles.

2. Review for Codestyle
- Carefully read the docs/dev/CODE_STYLE.md file, which explains the style rules of this project.
- Using this knowledge, diligently review the PR changes according to the style guides.

---

# When working on a new feature or an idea

1. Start from carefully reading the CLAUDE.md and README.md documents to get the context of this project
2. Then, read the docs/dev/SPECIFICATION.md document to deep dive into the technical details
3. Then, read the CHANGELOG.md to know what has been already shipped
4. IMPORTANT! Only after completion of those three steps, you may start working on a new feature requested by the user.