Skip to content

Conversation

@TabishB
Copy link
Contributor

@TabishB TabishB commented Oct 24, 2025

Summary

Adds Crush to the Native Slash Commands table in the README.

Context

Crush support was fully implemented in the codebase (including slash command configurator in src/core/configurators/slash/crush.ts and integration in the config), but was missing from the README documentation.

Changes

  • Added Crush entry to the "Native Slash Commands" table with its slash commands and command directory path

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Added Crush to the list of supported AI tools in native slash commands.

Add Crush to the Native Slash Commands table in the README. Crush support was implemented in the codebase but was missing from the documentation.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 24, 2025

Walkthrough

A new AI tool entry for "Crush" has been added to the "Supported AI Tools" native slash commands table in the README documentation. This is a straightforward documentation update with no logic or functionality changes.

Changes

Cohort / File(s) Change Summary
Documentation Update
README.md
Added a new row for Crush in the "Supported AI Tools" native slash commands table

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A new friend joins the table neat,
Crush arrives, the tools compete!
README glows with pride so bright,
One more ally in our sight! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The pull request title "docs: add Crush to supported AI tools in README" is fully aligned with the changeset. The raw summary confirms that a new row for Crush was added to the "Supported AI Tools" native slash commands table in README.md, and the PR objectives clarify that Crush support was implemented in the codebase but was missing from the documentation. The title uses the proper "docs:" prefix, is concise and specific, and clearly communicates the primary change without being vague or misleading.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/add-crush-to-readme

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5855fa2 and f5228b1.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🔇 Additional comments (1)
README.md (1)

97-97: Verify the Crush slash command syntax before merging.

The directory path (.crush/commands/openspec/) is correctly implemented and matches the file structure. However, the README lists the slash commands as /openspec-proposal, /openspec-apply, /openspec-archive (dash syntax), while the Crush frontmatter defines them as name: OpenSpec: Proposal (without explicit slash notation). Since CodeBuddy uses identical frontmatter formatting but the README lists it with colon syntax (/openspec:proposal), confirm whether Crush should also use colon syntax or if dash syntax is intentional and correct for the Crush tool.


Comment @coderabbitai help to get the list of available commands and usage tips.

@TabishB TabishB merged commit 5ab438f into main Oct 24, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants