feat: タスク完了時の通知機能を追加

[keito4]

Summary

• タスク完了時にbell.shスクリプトを実行してターミナルベル音を鳴らす機能を追加
• CLAUDE.mdにタスク完了通知の詳細な仕様を記載
• Slack通知と連携した包括的な通知システムを構築

Test plan

• bell.shスクリプトが正しく実行されることを確認
• タスク完了時にターミナルベル音が鳴ることを確認
• CLAUDE.mdの記載内容が正確であることを確認

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added a script that displays a completion message and plays a bell sound in the terminal when a task is finished.

• Documentation

  • Updated instructions to include the new bell notification step and clarified the sequence of task completion notifications. Added guidance for testing the completion sound.

[coderabbitai]

Walkthrough

A new shell script, .devcontainer/bell.sh, was added to output a Japanese completion message and play a terminal bell sound. Documentation in CLAUDE.md was updated to describe the bell script's role in task completion notifications, clarify notification steps, and update testing instructions to include verification of the bell sound.

Changes

File(s)	Change Summary
.devcontainer/bell.sh	Added a shell script to display a Japanese completion message and emit a terminal bell sound.
CLAUDE.md	Updated documentation to include bell script in notification steps and revised testing details.

Poem

The bell now rings, the task is done,
"タスクが完了しました"—completion's begun!
With a chime and a cheer,
The message is clear,
This rabbit’s work ends with a sound and some fun!
🛎️🐇

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.devcontainer/bell.sh (1)

1-3: Add strict-mode flags & portable shebang for safer execution

Running without set -euo pipefail makes it easy for the script to silently continue on errors (e.g. if printf fails in a non-TTY context).
Switching to #!/usr/bin/env bash also improves portability when /bin/bash is not present.

-#!/bin/bash
+#!/usr/bin/env bash
+set -euo pipefail

No functional change, but the script becomes more robust across environments.
Also double-check that the file is committed with the executable bit (chmod +x).

CLAUDE.md (1)

32-34: Hyphenate “to-do list” for correct grammar

Minor wording tweak.

- - Task status updates in the todo list
+ - Task status updates in the to-do list

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc3d84b and 13857e4.

📒 Files selected for processing (2)

• .devcontainer/bell.sh (1 hunks)
• CLAUDE.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

CLAUDE.md

[grammar] ~33-~33: It appears that a hyphen is missing in the noun “to-do” (= task) or did you mean the verb “to do”?
Context: ...d through: - Task status updates in the todo list - Bell notification script executi...

(TO_DO_HYPHEN)