Skip to content

docs: update skill files and add blasts skill#39

Merged
KalebCole merged 1 commit intomainfrom
sasha/update-skills
Mar 24, 2026
Merged

docs: update skill files and add blasts skill#39
KalebCole merged 1 commit intomainfrom
sasha/update-skills

Conversation

@KalebCole
Copy link
Copy Markdown
Owner

@KalebCole KalebCole commented Mar 24, 2026

Updates SKILL.md files to reflect current CLI state:

  • partiful-shared: Replaced bookmarklet auth with phone-based auth (partiful auth login <phone>). Documented auto SMS retrieval on macOS (via imsg), manual fallback, --code and --no-auto flags, E.164 format.
  • partiful-blasts: New skill for text blast command — documents --to statuses, 480 char limit, --dry-run, safety confirmation, and the SMS warning.
  • partiful-events and partiful-guests: Reviewed — already current, no changes needed.

Summary by CodeRabbit

  • Documentation
    • Added guide for partiful-blasts SMS text-sending commands with available flags and operational tips.
    • Updated authentication documentation for partiful auth login to reflect phone-based verification flow with new --code and --no-auto flags.

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 24, 2026

Warning

Rate limit exceeded

@KalebCole has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 4 minutes and 39 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a668e047-35d4-40e6-856f-d472a7cab179

📥 Commits

Reviewing files that changed from the base of the PR and between f83d409 and 433c7b3.

📒 Files selected for processing (2)
  • skills/partiful-blasts/SKILL.md
  • skills/partiful-shared/SKILL.md
📝 Walkthrough

Walkthrough

This 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

Cohort / File(s) Summary
New Blast Documentation
skills/partiful-blasts/SKILL.md
Added comprehensive skill documentation for the text-blast feature, including CLI usage syntax (partiful blasts send <eventId>), available flags (--message, --to, --show-on-event-page, --yes, --dry-run), valid recipient status values, and operational guidance.
Updated Auth Documentation
skills/partiful-shared/SKILL.md
Updated partiful auth login documentation to reflect phone-based authentication instead of bookmarklet flow, including E.164 phone format requirement, SMS verification behavior, macOS imsg auto-retrieval, and new CLI flags (--code, --no-auto).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Poem

🐰 Phone numbers now hop where tokens once dwelled,
SMS blasts send the tales to be told,
With flags and with formats, all carefully penned,
Our documentation—a skill that won't end! 📱✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main changes: updating skill documentation files and adding a new blasts skill documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch sasha/update-skills

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

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 imsg path and fallback, but it would be clearer to explicitly state that auto-retrieval requires imsg availability 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 for guests list examples.

Line 44 uses --status going (lowercase), while this doc lists uppercase enums for --to. A brief “case-insensitive” or “use lowercase for guests 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

📥 Commits

Reviewing files that changed from the base of the PR and between 6f1643f and f83d409.

📒 Files selected for processing (2)
  • skills/partiful-blasts/SKILL.md
  • skills/partiful-shared/SKILL.md


| Flag | Description |
|------|-------------|
| `--message <text>` | Message body (**max 480 characters**) |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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
@KalebCole KalebCole force-pushed the sasha/update-skills branch from f83d409 to 433c7b3 Compare March 24, 2026 14:47
@KalebCole KalebCole merged commit c46a4e0 into main Mar 24, 2026
1 check passed
@KalebCole KalebCole deleted the sasha/update-skills branch March 24, 2026 14:51
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.

1 participant