feat: add SubagentStop hook support and --local flag

[johnlindquist]

Summary

• Adds SubagentStop configuration to generated settings.json
• Adds --local flag to create settings.json.local for personal configuration
• Updates command description and examples to reflect new features

Test plan

• Unit tests pass for new functionality
• Added tests for SubagentStop in settings.json
• Added tests for --local flag functionality
• Linting passes
• Integration/smoke tests need to be run with built files

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added support for a new --local (-l) flag to create a local settings file (settings.json.local) during initialization.
  • Success messages now indicate whether a local settings file was created.
  • Introduced a new hook type, SubagentStop, in the default configuration.

• Tests

  • Expanded test coverage for the new --local flag and the SubagentStop hook.
  • Added tests to verify correct file creation and messaging when using the --local and --force flags.

[coderabbitai]

Walkthrough

The init command now supports a --local (-l) flag, allowing users to create a .claude/settings.json.local file instead of the default .claude/settings.json. The hook configuration adds a new SubagentStop type. Tests were updated to cover the new flag, file creation logic, and the updated hook configuration.

Changes

File(s)	Change Summary
src/commands/init.ts	Added --local flag, logic for .claude/settings.json.local, new SubagentStop hook, and updated messages.
test/commands/init.test.ts	Added tests for --local flag, checked for .local file creation, and validated new hook configuration.

Poem

A flag for the local, a file just for you,
Now init can split settings in two!
With SubagentStop joining the crew,
Tests hop along, verifying what's new.
In the warren of code, all is well—
🐇✨ Settings now ring a local bell!

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 093a7d1 and 189fefe.

📒 Files selected for processing (2)

• src/commands/init.ts (7 hunks)
• test/commands/init.test.ts (3 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`src/commands/**/*`: Commands must be implemented in the 'src/commands/' directory; currently, only the main 'init' command exists there.

src/commands/**/*: Commands must be implemented in the 'src/commands/' directory; currently, only the main 'init' command exists there.

📄 Source: CodeRabbit Inference Engine (CLAUDE.md)

List of files the instruction was applied to:

• src/commands/init.ts

🧠 Learnings (3)

📓 Common learnings

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to .claude/{settings.json,hooks/index.ts,hooks/lib.ts,hooks/session.ts} : The CLI generates a '.claude/' directory containing 'settings.json', 'hooks/index.ts', 'hooks/lib.ts', and 'hooks/session.ts' when initialized.

test/commands/init.test.ts (5)

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to **/*.integration.{ts,js} : Integration tests should test the full CLI behavior.

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to **/*.unit.{ts,js} : Unit tests should test individual commands and components.

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to .claude/{settings.json,hooks/index.ts,hooks/lib.ts,hooks/session.ts} : The CLI generates a '.claude/' directory containing 'settings.json', 'hooks/index.ts', 'hooks/lib.ts', and 'hooks/session.ts' when initialized.

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Tests must run on Ubuntu, Windows, and macOS with Node 18 & 20 in CI/CD.

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to src/commands/**/* : Commands must be implemented in the 'src/commands/' directory; currently, only the main 'init' command exists there.

src/commands/init.ts (2)

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to .claude/{settings.json,hooks/index.ts,hooks/lib.ts,hooks/session.ts} : The CLI generates a '.claude/' directory containing 'settings.json', 'hooks/index.ts', 'hooks/lib.ts', and 'hooks/session.ts' when initialized.

Learnt from: CR
PR: johnlindquist/claude-hooks#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-07T16:54:50.723Z
Learning: Applies to templates/**/* : Hook templates must be stored in the 'templates/' directory and are copied to the user's '.claude/' directory during initialization.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: test (macos-latest, 20)
• GitHub Check: test (ubuntu-latest, 20)
• GitHub Check: test (windows-latest, 18)
• GitHub Check: test (windows-latest, 20)
• GitHub Check: test (ubuntu-latest, 18)

🔇 Additional comments (14)

src/commands/init.ts (8)

12-13: Clear documentation of new features.

The updated description accurately reflects the new --local flag functionality and SubagentStop hook support. The documentation is clear and helpful for users.

---

26-30: Good example for the new --local flag.

The example follows the established pattern and clearly demonstrates how to use the new --local flag functionality.

---

38-42: Well-structured flag definition.

The local flag is properly defined with appropriate character alias, clear description, and correct help group placement.

---

82-82: Correct flag parameter passing.

The updateSettings method call properly passes the local flag value to enable the conditional file path logic.

---

92-94: Helpful conditional feedback message.

The conditional message provides clear feedback to users when the local settings file is created, enhancing the user experience.

---

215-215: Good method signature design.

The useLocal parameter with a default value of false maintains backward compatibility while enabling the new functionality.

---

216-216: Clean conditional file path logic.

The ternary operator clearly implements the file path selection based on the useLocal parameter.

---

276-286: Consistent hook configuration pattern.

The SubagentStop hook configuration follows the established pattern and maintains consistency with other hook types in the settings structure.

test/commands/init.test.ts (6)

32-32: Comprehensive help output testing.

The tests properly verify the --local flag appears in help output using both testing approaches, maintaining consistency with existing flag testing patterns.

Also applies to: 38-38

---

80-80: Proper hook property verification.

The test correctly verifies the SubagentStop hook property exists in the settings structure, maintaining consistency with other hook property tests.

---

88-92: Thorough hook structure verification.

The test properly verifies the SubagentStop hook has the correct command structure, following the established pattern for hook configuration testing.

---

167-180: Comprehensive --local flag functionality test.

The test thoroughly verifies the --local flag creates the correct file (settings.json.local) instead of the default, and includes proper content verification.

---

182-189: Important user feedback verification.

The test correctly verifies that the appropriate message about creating the local settings file is displayed to users, ensuring good user experience.

---

191-206: Solid flag combination testing.

The test properly verifies that the --local and --force flags work together correctly, ensuring both flag functionalities are preserved when combined.

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

[github-actions]

🎉 This PR is included in version 1.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀