add changelog

[harumiWeb]

• 今後の変更追跡のためのチェンジログを作成しました。
• AGENTS.mdを見直し、更新しました。

Summary by CodeRabbit

• Documentation
  • Added a changelog documenting project release history and updates.
  • Updated project workflow documentation to include a mandatory pre-implementation process covering requirements analysis, design review, specification definition, task assignment, implementation, review, testing, and documentation updates.

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation updates introducing a new mandatory workflow procedure in AGENTS.md with required task definition steps, and creation of a new CHANGELOG.md file to track project releases and changes in Japanese.

Changes

Cohort / File(s)	Summary
Documentation Updates AGENTS.md, CHANGELOG.md	AGENTS.md restructured to add new "2. 必要な作業手順" section defining pre-implementation workflow; existing sections renumbered accordingly. CHANGELOG.md introduced as new file with [Unreleased] section and v0.2.0 release entry dated 2026-03-29.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 ✨ A changelog hops into view,
With workflows new and structured true,
The docs now flow in ordered grace,
From spec to test, each in their place!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'add changelog' is concise and directly matches the main change: a new CHANGELOG.md file was added. However, it omits that AGENTS.md was also updated, which represents a secondary but meaningful change in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/update-notify

---

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 and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

AGENTS.md (1)

86-86: Step 3 is too narrow in scope.

The specification step currently states "関数の引数と戻り値の型を定義します" (define function arguments and return types), which is specific to code implementation. This workflow should also apply to documentation updates, configuration changes, and other non-code work that don't involve defining function signatures.

📝 Proposed generalization

-3. **仕様を定義する**：要件に基づいて、関数の引数と戻り値の型を定義します `tasks/feature_spec.md`。
+3. **仕様を定義する**：要件に基づいて、実装の仕様を定義します `tasks/feature_spec.md`。

This makes the step applicable to all types of work while maintaining the same structure.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 86, Update Step 3 in AGENTS.md to be broader: replace the
specific phrase "関数の引数と戻り値の型を定義します" with a generalized specification instruction
that covers code and non-code work (e.g., define inputs/outputs, acceptance
criteria, side effects, configuration changes, documentation updates, and
stakeholder expectations). Ensure the new text keeps the same structure and
references tasks/feature_spec.md but clarifies that specifications should
describe expected behavior, interfaces (if applicable), success criteria, and
any required environment or config changes so the step applies to documentation,
configs, and implementation work alike.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@AGENTS.md`:
- Line 86: Update Step 3 in AGENTS.md to be broader: replace the specific phrase
"関数の引数と戻り値の型を定義します" with a generalized specification instruction that covers
code and non-code work (e.g., define inputs/outputs, acceptance criteria, side
effects, configuration changes, documentation updates, and stakeholder
expectations). Ensure the new text keeps the same structure and references
tasks/feature_spec.md but clarifies that specifications should describe expected
behavior, interfaces (if applicable), success criteria, and any required
environment or config changes so the step applies to documentation, configs, and
implementation work alike.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8d2b7ac9-9564-4bc4-8b46-3632423da76e

📥 Commits

Reviewing files that changed from the base of the PR and between c9bc630 and b574379.

📒 Files selected for processing (2)

• AGENTS.md
• CHANGELOG.md