feat: contribute to Holdex repos using a structured Claude Code skill#100
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughAdded a new Claude command file ChangesHoldex contribution command + README
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Time Submission Status
You can submit time with the command. Example: See available commands to help comply with our Guidelines. |
|
@holdex pr submit-time 1h |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
README.md (1)
30-32: Use an idempotent symlink command for repeat setup runs.
ln -sfails if~/.claude/commandsalready exists. Use a safer one-liner so contributors can re-run setup without manual cleanup.Suggested doc update
- ln -s /path/to/holdex/developers/.claude/commands ~/.claude/commands + mkdir -p ~/.claude && ln -sfn /path/to/holdex/developers/.claude/commands ~/.claude/commands🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 30 - 32, Replace the fragile "ln -s /path/to/holdex/developers/.claude/commands ~/.claude/commands" example with an idempotent symlink one-liner: ensure the target directory (~/.claude) is created if missing and create or replace the symlink to /path/to/holdex/developers/.claude/commands using the force/replace options so repeated setup runs don't fail; update the README example line that currently shows "ln -s /path/to/holdex/developers/.claude/commands ~/.claude/commands" accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.claude/commands/holdex-contributing.md:
- Around line 6-8: Add a level-1 heading immediately after the existing front
matter block in the holdex-contributing markdown (e.g., insert "#
holdex-contributing" right after the front matter delimiter) to satisfy
markdownlint MD041; ensure the heading is the first content following the front
matter and does not alter the existing contributing text that follows.
- Around line 16-20: The markdown code block contains a single long line that
violates MD013 (80-char line length); split that long URL line into two wrapped
lines within the code block so it stays a valid list item and under 80
characters (e.g., break the URL after a logical separator or split the list item
into the dash line and the URL on the next indented line). Update the example
list item in the code block under the guidance section so the long line is
wrapped to satisfy MD013 while preserving the bullet (`-`) and the referenced
URL text.
- Around line 11-14: Update the “Good” example to include the required prefix so
it matches the rule "Name: `Problem: [statement]`" — change the good example
from `employees can't safely handle fund disbursements` to `Problem: employees
can't safely handle fund disbursements` so the guidance is consistent; ensure
the text in the doc that currently shows the Good example is replaced with the
prefixed version.
---
Nitpick comments:
In `@README.md`:
- Around line 30-32: Replace the fragile "ln -s
/path/to/holdex/developers/.claude/commands ~/.claude/commands" example with an
idempotent symlink one-liner: ensure the target directory (~/.claude) is created
if missing and create or replace the symlink to
/path/to/holdex/developers/.claude/commands using the force/replace options so
repeated setup runs don't fail; update the README example line that currently
shows "ln -s /path/to/holdex/developers/.claude/commands ~/.claude/commands"
accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: d6729cd2-3382-47d0-8135-af2f0104429e
📒 Files selected for processing (2)
.claude/commands/holdex-contributing.mdREADME.md
| All PRs and issues must follow the | ||
| [Holdex Contributing Guidelines](https://github.com/holdex/developers/blob/main/docs/CONTRIBUTING.md). | ||
|
|
There was a problem hiding this comment.
Add a level-1 heading after front matter.
Markdownlint MD041 is valid here. Add a top-level heading (for example # holdex-contributing) right after the front matter block.
🧰 Tools
🪛 GitHub Check: checks
[warning] 6-6: MD041
First line in file should be a level 1 heading
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/commands/holdex-contributing.md around lines 6 - 8, Add a level-1
heading immediately after the existing front matter block in the
holdex-contributing markdown (e.g., insert "# holdex-contributing" right after
the front matter delimiter) to satisfy markdownlint MD041; ensure the heading is
the first content following the front matter and does not alter the existing
contributing text that follows.
| - Name: `Problem: [statement]` — must be a **job story** describing what a | ||
| specific user **cannot do** (the whole title under 65 characters). | ||
| - Good: `employees can't safely handle fund disbursements` | ||
| - Bad: `fund handling issue` |
There was a problem hiding this comment.
Make the “Good” issue example match the required format.
You require Problem: [statement], but the “Good” example omits the Problem: prefix. Update it to avoid contradictory guidance.
Suggested doc update
- - Good: `employees can't safely handle fund disbursements`
+ - Good: `Problem: employees can't safely handle fund disbursements`🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.claude/commands/holdex-contributing.md around lines 11 - 14, Update the
“Good” example to include the required prefix so it matches the rule "Name:
`Problem: [statement]`" — change the good example from `employees can't safely
handle fund disbursements` to `Problem: employees can't safely handle fund
disbursements` so the guidance is consistent; ensure the text in the doc that
currently shows the Good example is replaced with the prefixed version.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 31-33: Update the README.md symlink instructions to first ensure
the target directory exists and then create a deterministic symlink: add a step
to create the ~/.claude directory if missing (use a mkdir -p style command) and
replace the plain ln -s with an ln invocation that forcefully replaces existing
links/targets (use options equivalent to -sfn) so ~/.claude/commands (the symbol
shown in the diff) is never left as a nested directory or broken symlink; update
the example line that references /path/to/holdex/developers/.claude/commands to
reflect these two steps.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ```bash | ||
| ln -s /path/to/holdex/developers/.claude/commands ~/.claude/commands | ||
| ``` |
There was a problem hiding this comment.
Harden the symlink setup command to avoid common setup failures.
On Line 32, ln -s ... ~/.claude/commands can fail (missing ~/.claude) or create an unexpected nested link if ~/.claude/commands already exists as a directory. A safer sequence will reduce onboarding issues.
Suggested doc update
```bash
-ln -s /path/to/holdex/developers/.claude/commands ~/.claude/commands
+mkdir -p ~/.claude
+ln -sfn /path/to/holdex/developers/.claude/commands ~/.claude/commands</details>
<!-- suggestion_start -->
<details>
<summary>📝 Committable suggestion</summary>
> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
```suggestion
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` around lines 31 - 33, Update the README.md symlink instructions to
first ensure the target directory exists and then create a deterministic
symlink: add a step to create the ~/.claude directory if missing (use a mkdir -p
style command) and replace the plain ln -s with an ln invocation that forcefully
replaces existing links/targets (use options equivalent to -sfn) so
~/.claude/commands (the symbol shown in the diff) is never left as a nested
directory or broken symlink; update the example line that references
/path/to/holdex/developers/.claude/commands to reflect these two steps.
|
https://github.com/holdex pr submit-time 1h 20m |
2 participants
Summary
.claude/commands/holdex-contributing.md— a/holdex-contributingskill for Claude CodeCONTRIBUTING.md(issue naming, PR title format, PR lifecycle) so contributors can invoke it on demand before creating or updating issues and PRsUsage
Run
/holdex-contributingin Claude Code before creating or updating a GitHub issue or PR in any Holdex repository.🤖 Generated with Claude Code
Summary by CodeRabbit