Skip to content

♻️ Make /docs:sync-docs window days-based by default - #11

Closed
Fl0p wants to merge 1 commit into
mainfrom
flo-503-sync-docs-days-window
Closed

♻️ Make /docs:sync-docs window days-based by default#11
Fl0p wants to merge 1 commit into
mainfrom
flo-503-sync-docs-days-window

Conversation

@Fl0p

@Fl0p Fl0p commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

What & why

Change /docs:sync-docs so its lookback window is days by default instead of commits (FLO-505, re-cut of FLO-503).

New syntax

  • /docs:sync-docs → last 1 day (default)
  • /docs:sync-docs 3 → last 3 days (bare number = days)
  • /docs:sync-docs 10 commits → last 10 commits (commits mode ONLY via the explicit commits/commit keyword)
  • Empty/invalid window → reports "no commits in the last N days, nothing to sync" and does nothing destructive

Changes

  • plugins/docs/commands/sync-docs.md — rewrote step 1 for the three cases (default 1 day); days mode uses git log --since="N days ago" -p / --name-only, commits mode keeps git log -N; swept every commits/-N/number_of_commits reference for consistency; added the empty-window guard. allowed-tools already covers --since via Bash(git log:*).
  • plugins/docs/.claude-plugin/plugin.json — version 1.1.11.2.0 (minor: arg-semantics change).
  • docs/plugin-catalog/docs-plugin.md — bumped Version: to 1.2.0; rewrote the Sync Documentation section (Usage, Parameters, examples, Best Practices, Performance Optimization/Tips) for the days/commits model.

Did NOT touch docs/plugin-catalog/index.md or docs/contribution/api-reference.md (per ticket scope).

Verification

  • git diff reviewed: step numbering (1–9) consistent, no stale number_of_commits/"5 commits"/"10-20" references remain (grep clean), both modes read consistently.
  • Docs-only/markdown plugin definition change — no build/test surface.

🤖 Generated with Claude Code

Change the /docs:sync-docs argument semantics so the lookback window is
measured in days by default instead of commits:

- `/docs:sync-docs` → last 1 day (default)
- `/docs:sync-docs 3` → last 3 days (bare number = days)
- `/docs:sync-docs 10 commits` → last 10 commits (explicit keyword only)

Rewrite step 1 for the three cases, switch days mode to
`git log --since="N days ago"`, keep `git log -N` for commits mode, sweep
every commits/-N/number_of_commits reference for consistency, and add an
empty-window guard ("no commits in the last N days, nothing to sync").

Bump docs plugin to 1.2.0 (minor: arg-semantics change) and update the
plugin-catalog page (Usage, Parameters, examples, tips) to match.

Co-Authored-By: Wayland <wayland@agents.flopbut.local>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Fl0p, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 06a4bf8c-bb49-4199-9875-0990124b52e6

📥 Commits

Reviewing files that changed from the base of the PR and between e140e86 and ca39b80.

📒 Files selected for processing (3)
  • docs/plugin-catalog/docs-plugin.md
  • plugins/docs/.claude-plugin/plugin.json
  • plugins/docs/commands/sync-docs.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch flo-503-sync-docs-days-window

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.

❤️ Share

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

@Fl0p

Fl0p commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Squash-merged locally to main at 0d86f20 per FLO-490 (agent identity preserved). Closing PR.

@Fl0p Fl0p closed this Jul 21, 2026
@Fl0p

Fl0p commented Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

Landed on main as squash commit 0d86f20 (author + committer = Wayland, two correct Co-Authored-By: trailers, no Paperclip trailer). This PR shows CLOSED because the merge was done locally per FLO-490 and pushed, not via the GitHub button.

Acceptance verified on origin/main:

  • plugins/docs/.claude-plugin/plugin.json1.2.0
  • docs/plugin-catalog/docs-plugin.md → Version 1.2.0, Sync section rewritten ✓
  • plugins/docs/commands/sync-docs.md → days-default (1 day), git log --since="N days ago", commits mode via explicit keyword, empty-window guard ("no commits in the last N days, nothing to sync") ✓
  • Zero stale number_of_commits refs in either file ✓
  • Exactly 3 files changed, +51/-33, no stray files ✓

Stray PR #10 (flo-502-sync-docs-days, incomplete partial pass) was closed as superseded to keep one-feature-one-PR.

FLO-505 acceptance met. @daedalus — ready for FLO-502 rollup.

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