docs: update skill files and add blasts skill#39
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
⌛ 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis pull request adds new documentation for the "partiful-blasts" skill and updates the "partiful-shared" skill documentation. The changes document CLI commands for sending SMS text blasts with configurable flags and update the authentication flow from bookmarklet-based to phone-number-based with SMS verification. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
skills/partiful-shared/SKILL.md (1)
18-19: Clarify prerequisites and non-macOS behavior for auto-retrieval.Line 18 and Line 19 describe the macOS
imsgpath and fallback, but it would be clearer to explicitly state that auto-retrieval requiresimsgavailability and that non-macOS always uses manual entry (or--code). This avoids operator confusion during first-time setup.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/partiful-shared/SKILL.md` around lines 18 - 19, Update the documentation near the macOS auto-retrieval description to explicitly state that automatic code retrieval requires the `imsg` tool/service to be installed and accessible (i.e., `imsg` must be available on macOS), and clarify that on non-macOS systems auto-retrieval is not supported—operators must enter the code manually or supply it via the `--code` option; modify the text around the `imsg` and fallback lines to include these prerequisites and non-macOS behavior.skills/partiful-blasts/SKILL.md (1)
44-44: Add a short note on status value casing forguests listexamples.Line 44 uses
--status going(lowercase), while this doc lists uppercase enums for--to. A brief “case-insensitive” or “use lowercase forguests list” note would reduce copy/paste mistakes.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/partiful-blasts/SKILL.md` at line 44, Add a short note clarifying the expected casing for the guests list status to avoid copy/paste errors: update the text around the "Combine with `partiful guests list <eventId> --status going`" example to state that the `--status` flag (used with `guests list`) is case-insensitive or should be provided in lowercase, and contrast this with the uppercase enum style used for the `--to` values so readers know the difference between `--status` and `--to`.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/partiful-blasts/SKILL.md`:
- Line 20: Clarify that the 480-character limit applies to the final rendered
SMS including any auto-prefixed text (not just the user-provided --message),
update the description of the `--message` flag and the prefix note (referenced
near the prefix statement and the two mentions on lines 20 and 42) to explicitly
say "480 characters total including auto-prefixed text", and add a short note
about trimming/validation behavior (e.g., message will be rejected or truncated
if the combined length exceeds 480) so callers know how the combined length is
enforced.
---
Nitpick comments:
In `@skills/partiful-blasts/SKILL.md`:
- Line 44: Add a short note clarifying the expected casing for the guests list
status to avoid copy/paste errors: update the text around the "Combine with
`partiful guests list <eventId> --status going`" example to state that the
`--status` flag (used with `guests list`) is case-insensitive or should be
provided in lowercase, and contrast this with the uppercase enum style used for
the `--to` values so readers know the difference between `--status` and `--to`.
In `@skills/partiful-shared/SKILL.md`:
- Around line 18-19: Update the documentation near the macOS auto-retrieval
description to explicitly state that automatic code retrieval requires the
`imsg` tool/service to be installed and accessible (i.e., `imsg` must be
available on macOS), and clarify that on non-macOS systems auto-retrieval is not
supported—operators must enter the code manually or supply it via the `--code`
option; modify the text around the `imsg` and fallback lines to include these
prerequisites and non-macOS behavior.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 812dfb97-6dba-43ee-96b7-e8651e2669bd
📒 Files selected for processing (2)
skills/partiful-blasts/SKILL.mdskills/partiful-shared/SKILL.md
|
|
||
| | Flag | Description | | ||
| |------|-------------| | ||
| | `--message <text>` | Message body (**max 480 characters**) | |
There was a problem hiding this comment.
Specify whether the 480-character limit is before or after the auto-prefixed text.
Line 20 and Line 42 mention the limit, while Line 8 states a prefix is added. Please clarify if the 480 limit applies to user-provided --message only, or the final rendered SMS content including prefix.
Also applies to: 42-42
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/partiful-blasts/SKILL.md` at line 20, Clarify that the 480-character
limit applies to the final rendered SMS including any auto-prefixed text (not
just the user-provided --message), update the description of the `--message`
flag and the prefix note (referenced near the prefix statement and the two
mentions on lines 20 and 42) to explicitly say "480 characters total including
auto-prefixed text", and add a short note about trimming/validation behavior
(e.g., message will be rejected or truncated if the combined length exceeds 480)
so callers know how the combined length is enforced.
- partiful-shared: Replace bookmarklet auth with phone-based auth flow (partiful auth login <phone>), document auto SMS retrieval via imsg, --code and --no-auto flags, E.164 format requirement - partiful-blasts: New skill documenting text blast command with --to statuses, 480 char limit, --dry-run, safety confirmation - partiful-events and partiful-guests: Reviewed, no changes needed
f83d409 to
433c7b3
Compare
Updates SKILL.md files to reflect current CLI state:
partiful auth login <phone>). Documented auto SMS retrieval on macOS (via imsg), manual fallback,--codeand--no-autoflags, E.164 format.--tostatuses, 480 char limit,--dry-run, safety confirmation, and the SMS warning.Summary by CodeRabbit
--codeand--no-autoflags.