chore(config): Move commands to .agents directory and add symlinks#826
chore(config): Move commands to .agents directory and add symlinks#826
Conversation
Moved all command files from .claude/commands to .agents/commands to standardize the agents directory structure. Added symlinks in .claude/commands and .cursor/commands to maintain backward compatibility.
WalkthroughAdds two new command pointer files for AI/tooling configurations: .claude/commands and .cursor/commands. Both reference ../.agents/commands, with .cursor/commands containing that path as its single line. No executable logic or public API changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Pre-merge checks (3 passed)✅ Passed checks (3 passed)
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. ✨ Finishing Touches🧪 Generate unit tests
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. Comment |
There was a problem hiding this comment.
Pull Request Overview
This PR reorganizes the project's AI agent configuration by moving command files from .claude/commands to .agents/commands and creating symlinks for backward compatibility.
Key Changes
- Standardizes AI agent configuration under the
.agents/directory - Creates symlinks in
.claude/commandsand.cursor/commandspointing to the new location - Maintains backward compatibility for existing tooling
Reviewed Changes
Copilot reviewed 2 out of 10 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .cursor/commands | Creates symlink to standardized .agents/commands directory |
| .claude/commands | Creates symlink to standardized .agents/commands directory |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @yamadashy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request refactors the project's command file organization by migrating them to a new, centralized directory. The primary goal is to standardize the location for AI agent-related commands, ensuring a consistent and scalable structure while maintaining full compatibility for existing workflows through strategic use of symlinks.
Highlights
- Directory Structure Standardization: All command files have been moved from the legacy .claude/commands directory to the new, standardized .agents/commands directory. This centralizes AI agent-related configurations.
- Backward Compatibility: Symlinks have been created in the original .claude/commands and .cursor/commands locations, pointing to the new .agents/commands directory. This ensures that existing tooling continues to function without disruption.
- Improved Organization: The change aligns with the project's goal of using .agents/ as the primary location for all AI agent-related assets, improving overall project organization and maintainability.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Code Review
This pull request aims to reorganize command files into the .agents directory and maintain backward compatibility using symlinks. However, the implementation for the symlinks appears to be incorrect. Instead of creating symbolic links, the changes add regular text files containing the target path. This will likely break any tooling that expects .claude/commands and .cursor/commands to be directories. My review includes critical feedback on how to fix this by creating proper symlinks that Git can track.
Deploying repomix with
|
| Latest commit: |
695fedf
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3245f50c.repomix.pages.dev |
| Branch Preview URL: | https://chore-agents-commands.repomix.pages.dev |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #826 +/- ##
=======================================
Coverage 87.36% 87.36%
=======================================
Files 113 113
Lines 6626 6626
Branches 1372 1372
=======================================
Hits 5789 5789
Misses 837 837 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
.claude/commands (1)
1-1: Symlink configuration verified
Both.claude/commandsand.cursor/commandsare committed as mode 120000 symlinks pointing to../.agents/commands, and the target directory exists.
Optional: add a note in CONTRIBUTING.md about enabling symlinks on Windows to avoid tooling breakage..cursor/commands (1)
1-1: Windows devs may need guidance for symlinks.On Windows, symlinks can require Developer Mode or elevated perms; otherwise Git may check out a plain file. Consider adding a short note in CONTRIBUTING.md about enabling symlinks or providing a fallback.
I can draft a brief CONTRIBUTING snippet covering Git core.symlinks and Windows Developer Mode if helpful.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.claude/commands(1 hunks).cursor/commands(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-18T15:12:57.179Z
Learnt from: CR
PR: yamadashy/repomix#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T15:12:57.179Z
Learning: .agents/rules/base.md
Applied to files:
.claude/commands.cursor/commands
⏰ 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). (2)
- GitHub Check: Test with Bun (windows-latest, latest)
- GitHub Check: Build and run (windows-latest, 22.x)
🔇 Additional comments (2)
.cursor/commands (2)
1-1: Relative path looks correct from .cursor to .agents.../.agents/commands correctly resolves from .cursor/commands to the repo-level .agents/commands directory.
1-1: Symlinks correctly configured
Both.cursor/commandsand.claude/commandsare Git-mode 120000 symlinks to../.agents/commands, and the target exists as a directory.
This PR moves all command files from
.claude/commandsto.agents/commandsto standardize the agents directory structure and improve organization.Changes
.claude/commands/to.agents/commands/.claude/commandsand.cursor/commandspointing to.agents/commands.claude/commandsThis change aligns with the project's move towards using the
.agents/directory as the standard location for AI agent-related configuration and commands.Checklist
npm run testnpm run lint