Skip to content

docs: add draw.io flow diagram for the skill - #6

Merged
phj6688 merged 1 commit into
mainfrom
docs/skill-flow-diagram
Jul 10, 2026
Merged

phj6688 merged 1 commit into
mainfrom
docs/skill-flow-diagram

Conversation

@phj6688

@phj6688 phj6688 commented Jul 10, 2026

Copy link
Copy Markdown
Owner

Adds docs/linear-issue-craft-flow.drawio, a one-page map of what the skill does end to end so a new user can see the whole pipeline at a glance.

What it shows

  • TriggerClassify (archetype decision tree: Epic / Story / Hardening / Task / decompose, plus interactive vs headless mode) → DraftValidate (Gate 1 validator, Gate 2 judgment, Gate 3 independent reviewer, or the save-hook in headless mode) → File (save_issue, with the PreToolUse gate re-check).
  • The Anchor primitive and where the held-out probe binds.
  • The downstream compiler pipeline the issue feeds (planner, held-out probe, implementer, reviewer, merge gate) that explains why concreteness is the product.
  • The nine golden rules as a footer.

Themed to the house palette. Also linked from the README and noted in the CHANGELOG.

Docs-only: no code paths touched, so CI (skill/manifest validation, ruff, tests) is unaffected.

One-page map of the skill end to end: trigger, classify archetype and detect mode, draft, the three gates (or save-hook in headless mode), file. Includes the downstream compiler pipeline and the golden rules. Linked from the README.
@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 20 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 438ea54c-7d80-4560-8d7c-11fac20ae48b

📥 Commits

Reviewing files that changed from the base of the PR and between 4b4287a and 2febced.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • README.md
  • docs/linear-issue-craft-flow.drawio
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/skill-flow-diagram

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

@phj6688
phj6688 merged commit 544b596 into main Jul 10, 2026
7 checks passed
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