@su-record/vibe 2.9.21 → 2.9.23

package/skills/commit-push-pr/agents/reviewer.md

@@ -1,52 +1,52 @@
----
-name: reviewer
-role: Reviews commit message and PR body for quality before submission
-tools: [Read, Bash]
----
-
-# Reviewer
-
-## Role
-Final quality gate before the commit is created and the PR is opened. Checks that the commit message and PR body meet quality standards and accurately reflect the change analysis. Blocks submission if critical issues are found.
-
-## Responsibilities
-- Verify commit subject line follows Conventional Commits format and is under 72 chars
-- Check that commit body explains motivation, not just what changed
-- Confirm PR title is under 70 characters and matches the commit type
-- Verify PR body has all required sections: Summary, Motivation, Test Plan
-- Flag missing BREAKING CHANGE footer if analysis identified API/behavior changes
-
-## Input
-- Commit message from message-writer
-- PR title and body from pr-writer
-- Change analysis report from change-analyzer (ground truth)
-
-## Output
-Quality review verdict:
-
-```markdown
-## Commit/PR Review
-
-### Commit Message
-- [x] Conventional format: fix(auth): ...
-- [x] Subject under 72 chars (61 chars)
-- [x] Body explains motivation
-- [ ] MISSING: BREAKING CHANGE footer — validateToken now returns null, not throws
-
-### PR Body
-- [x] Title under 70 chars
-- [x] Summary section present (3 bullets)
-- [x] Motivation section present
-- [x] Test Plan has manual verification step
-- [ ] MISSING: Notes section should document null-vs-throw behavior change
-
-### Verdict
-BLOCKED — 2 items must be fixed before submission.
-```
-
-## Communication
-- Reports findings to: orchestrator (commit-push-pr skill) / user
-- Receives instructions from: orchestrator
-
-## Domain Knowledge
-BLOCKED verdict requires fix before proceeding. APPROVED verdict allows immediate submission. A BREAKING CHANGE in the diff that is not documented in the commit footer is always a blocker. "What changed" in PR body is informational; "Why it changed" is required.
+---
+name: reviewer
+role: Reviews commit message and PR body for quality before submission
+tools: [Read, Bash]
+---
+
+# Reviewer
+
+## Role
+Final quality gate before the commit is created and the PR is opened. Checks that the commit message and PR body meet quality standards and accurately reflect the change analysis. Blocks submission if critical issues are found.
+
+## Responsibilities
+- Verify commit subject line follows Conventional Commits format and is under 72 chars
+- Check that commit body explains motivation, not just what changed
+- Confirm PR title is under 70 characters and matches the commit type
+- Verify PR body has all required sections: Summary, Motivation, Test Plan
+- Flag missing BREAKING CHANGE footer if analysis identified API/behavior changes
+
+## Input
+- Commit message from message-writer
+- PR title and body from pr-writer
+- Change analysis report from change-analyzer (ground truth)
+
+## Output
+Quality review verdict:
+
+```markdown
+## Commit/PR Review
+
+### Commit Message
+- [x] Conventional format: fix(auth): ...
+- [x] Subject under 72 chars (61 chars)
+- [x] Body explains motivation
+- [ ] MISSING: BREAKING CHANGE footer — validateToken now returns null, not throws
+
+### PR Body
+- [x] Title under 70 chars
+- [x] Summary section present (3 bullets)
+- [x] Motivation section present
+- [x] Test Plan has manual verification step
+- [ ] MISSING: Notes section should document null-vs-throw behavior change
+
+### Verdict
+BLOCKED — 2 items must be fixed before submission.
+```
+
+## Communication
+- Reports findings to: orchestrator (commit-push-pr skill) / user
+- Receives instructions from: orchestrator
+
+## Domain Knowledge
+BLOCKED verdict requires fix before proceeding. APPROVED verdict allows immediate submission. A BREAKING CHANGE in the diff that is not documented in the commit footer is always a blocker. "What changed" in PR body is informational; "Why it changed" is required.

package/skills/commit-push-pr/rubrics/commit-message.md

@@ -1,73 +1,73 @@
-# Commit Message Format Rubric
-
-## Structure
-
-```
-<type>(<scope>): <subject>          ← 50 chars max, imperative mood
-                                    ← blank line
-<body>                              ← 72 chars/line wrap, explain WHY
-                                    ← blank line
-<footer>                            ← Co-Authored-By, Closes #N
-```
-
-## Types
-
-| Type | When to Use |
-|------|-------------|
-| `feat` | New feature or capability |
-| `fix` | Bug fix |
-| `refactor` | Code restructure, no behavior change |
-| `perf` | Performance improvement |
-| `test` | Adding or fixing tests |
-| `docs` | Documentation only |
-| `style` | Formatting, whitespace (no logic change) |
-| `chore` | Build, deps, tooling, CI |
-
-## Subject Line Rules
-
-- Imperative mood: "add feature" not "added feature"
-- No period at end
-- Max 50 characters
-- Scope is optional: `feat(auth): add OAuth login`
-
-## Body Rules
-
-- Explain **why**, not what (code shows what)
-- Wrap at 72 characters
-- Use bullet points for multiple changes
-- Reference issues: `Closes #123`, `Fixes #456`
-
-## Required Footer
-
-```
-Co-Authored-By: Claude <noreply@anthropic.com>
-```
-
-## Examples
-
-```
-feat(auth): add GitHub OAuth login
-
-Users can now sign in with GitHub instead of email/password.
-Reduces friction for developer-focused onboarding flow.
-
-Closes #42
-Co-Authored-By: Claude <noreply@anthropic.com>
-```
-
-```
-fix(api): prevent null reference on empty search results
-
-The search endpoint crashed when no results matched.
-Added early return with empty array instead.
-
-Co-Authored-By: Claude <noreply@anthropic.com>
-```
-
-## Rejection Criteria
-
-- Subject over 50 chars
-- Missing Co-Authored-By line
-- Past tense in subject ("added", "fixed")
-- Subject with period at end
-- No body when change is non-trivial
+# Commit Message Format Rubric
+
+## Structure
+
+```
+<type>(<scope>): <subject>          ← 50 chars max, imperative mood
+                                    ← blank line
+<body>                              ← 72 chars/line wrap, explain WHY
+                                    ← blank line
+<footer>                            ← Co-Authored-By, Closes #N
+```
+
+## Types
+
+| Type | When to Use |
+|------|-------------|
+| `feat` | New feature or capability |
+| `fix` | Bug fix |
+| `refactor` | Code restructure, no behavior change |
+| `perf` | Performance improvement |
+| `test` | Adding or fixing tests |
+| `docs` | Documentation only |
+| `style` | Formatting, whitespace (no logic change) |
+| `chore` | Build, deps, tooling, CI |
+
+## Subject Line Rules
+
+- Imperative mood: "add feature" not "added feature"
+- No period at end
+- Max 50 characters
+- Scope is optional: `feat(auth): add OAuth login`
+
+## Body Rules
+
+- Explain **why**, not what (code shows what)
+- Wrap at 72 characters
+- Use bullet points for multiple changes
+- Reference issues: `Closes #123`, `Fixes #456`
+
+## Required Footer
+
+```
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+## Examples
+
+```
+feat(auth): add GitHub OAuth login
+
+Users can now sign in with GitHub instead of email/password.
+Reduces friction for developer-focused onboarding flow.
+
+Closes #42
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+```
+fix(api): prevent null reference on empty search results
+
+The search endpoint crashed when no results matched.
+Added early return with empty array instead.
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+## Rejection Criteria
+
+- Subject over 50 chars
+- Missing Co-Authored-By line
+- Past tense in subject ("added", "fixed")
+- Subject with period at end
+- No body when change is non-trivial

package/skills/commit-push-pr/templates/pr-body.md

@@ -1,63 +1,63 @@
-# PR Body Template
-
-Use this template with `gh pr create --body "$(cat <<'EOF' ... EOF)"`.
-
----
-
-## Summary
-
-- {{CHANGE_1}}
-- {{CHANGE_2}}
-- {{CHANGE_3}}
-
-## Motivation
-
-{{WHY_THIS_CHANGE — business reason or problem being solved}}
-
-## Related Issues
-
-- Closes #{{ISSUE_NUMBER}}
-
-## Test Plan
-
-- [ ] {{TEST_STEP_1}}
-- [ ] {{TEST_STEP_2}}
-- [ ] {{TEST_STEP_3}}
-
-## Screenshots / Demo
-
-{{ATTACH_SCREENSHOT_OR_REMOVE_SECTION}}
-
----
-
-{{SESSION_URL}}
-
----
-
-## Usage Notes
-
-**Minimal PR (bug fix, chore):**
-
-```
-## Summary
-- {{CHANGE}}
-
-## Related Issues
-- Fixes #{{ISSUE_NUMBER}}
-
-{{SESSION_URL}}
-```
-
-**Feature PR:**
-
-Use the full template above. Screenshots required for UI changes.
-
-**Breaking Change:**
-
-Add this section at the top:
-
-```
-## BREAKING CHANGE
-
-{{WHAT_BREAKS}} — {{MIGRATION_STEPS}}
-```
+# PR Body Template
+
+Use this template with `gh pr create --body "$(cat <<'EOF' ... EOF)"`.
+
+---
+
+## Summary
+
+- {{CHANGE_1}}
+- {{CHANGE_2}}
+- {{CHANGE_3}}
+
+## Motivation
+
+{{WHY_THIS_CHANGE — business reason or problem being solved}}
+
+## Related Issues
+
+- Closes #{{ISSUE_NUMBER}}
+
+## Test Plan
+
+- [ ] {{TEST_STEP_1}}
+- [ ] {{TEST_STEP_2}}
+- [ ] {{TEST_STEP_3}}
+
+## Screenshots / Demo
+
+{{ATTACH_SCREENSHOT_OR_REMOVE_SECTION}}
+
+---
+
+{{SESSION_URL}}
+
+---
+
+## Usage Notes
+
+**Minimal PR (bug fix, chore):**
+
+```
+## Summary
+- {{CHANGE}}
+
+## Related Issues
+- Fixes #{{ISSUE_NUMBER}}
+
+{{SESSION_URL}}
+```
+
+**Feature PR:**
+
+Use the full template above. Screenshots required for UI changes.
+
+**Breaking Change:**
+
+Add this section at the top:
+
+```
+## BREAKING CHANGE
+
+{{WHAT_BREAKS}} — {{MIGRATION_STEPS}}
+```

package/skills/context7-usage/SKILL.md

@@ -1,106 +1,106 @@
----
-name: context7-usage
-tier: optional
-description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
-triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
-priority: 60
----
-
-# Context7 Usage
-
-Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
-
-## Why Subagent Approach?
-
-| Approach | Problem |
-|----------|---------|
-| Direct plugin call | Docs content fills main context, causing bloat |
-| Subagent isolation | Docs queried in separate context, only results returned |
-
-**Benefits:**
-
-- Prevents context bloat during long coding sessions
-- Solves knowledge cutoff problem with latest docs
-- Main context stays focused on implementation
-
-## When to Use
-
-| Situation | Example |
-|-----------|---------|
-| Latest API check | "React 19 use() hook usage" |
-| Version differences | "Next.js 15 changes" |
-| Official docs needed | "Prisma schema syntax" |
-| Migration guide | "Vue 2 → Vue 3 migration" |
-
-## How It Works
-
-```
-User asks library question
-    ↓
-Skill detects docs need
-    ↓
-Spawn docs-researcher subagent (haiku)
-    ↓
-Subagent calls context7 in isolated context
-    ↓
-Returns only relevant info to main context
-```
-
-## Usage
-
-### Automatic (Recommended)
-
-Just ask library/API questions naturally:
-
-```
-"How do I use React 19 use() hook?"
-"What's new in Next.js 15?"
-"Prisma many-to-many relation syntax"
-```
-
-The skill auto-detects and spawns a docs-researcher subagent.
-
-### Manual Command
-
-```
-/context7:docs <library> [query]
-```
-
-Examples:
-
-```
-/context7:docs react hooks
-/context7:docs next.js app router
-/context7:docs prisma relations
-```
-
-## Implementation Pattern
-
-When you detect a library/API documentation need, spawn a subagent:
-
-```
-Task tool call:
-- subagent_type: Explore
-- model: haiku
-- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
-```
-
-The subagent handles the context7 calls and returns a summary, keeping main context clean.
-
-## Fallback Chain
-
-```
-context7 plugin not installed
-    ↓
-Prompt user: /plugin install context7
-    ↓
-If still unavailable: Web Search for official docs
-```
-
-## Installation
-
-If context7 is not installed, guide user:
-
-```bash
-/plugin install context7
-```
+---
+name: context7-usage
+tier: optional
+description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
+triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
+priority: 60
+---
+
+# Context7 Usage
+
+Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
+
+## Why Subagent Approach?
+
+| Approach | Problem |
+|----------|---------|
+| Direct plugin call | Docs content fills main context, causing bloat |
+| Subagent isolation | Docs queried in separate context, only results returned |
+
+**Benefits:**
+
+- Prevents context bloat during long coding sessions
+- Solves knowledge cutoff problem with latest docs
+- Main context stays focused on implementation
+
+## When to Use
+
+| Situation | Example |
+|-----------|---------|
+| Latest API check | "React 19 use() hook usage" |
+| Version differences | "Next.js 15 changes" |
+| Official docs needed | "Prisma schema syntax" |
+| Migration guide | "Vue 2 → Vue 3 migration" |
+
+## How It Works
+
+```
+User asks library question
+    ↓
+Skill detects docs need
+    ↓
+Spawn docs-researcher subagent (haiku)
+    ↓
+Subagent calls context7 in isolated context
+    ↓
+Returns only relevant info to main context
+```
+
+## Usage
+
+### Automatic (Recommended)
+
+Just ask library/API questions naturally:
+
+```
+"How do I use React 19 use() hook?"
+"What's new in Next.js 15?"
+"Prisma many-to-many relation syntax"
+```
+
+The skill auto-detects and spawns a docs-researcher subagent.
+
+### Manual Command
+
+```
+/context7:docs <library> [query]
+```
+
+Examples:
+
+```
+/context7:docs react hooks
+/context7:docs next.js app router
+/context7:docs prisma relations
+```
+
+## Implementation Pattern
+
+When you detect a library/API documentation need, spawn a subagent:
+
+```
+Task tool call:
+- subagent_type: Explore
+- model: haiku
+- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
+```
+
+The subagent handles the context7 calls and returns a summary, keeping main context clean.
+
+## Fallback Chain
+
+```
+context7 plugin not installed
+    ↓
+Prompt user: /plugin install context7
+    ↓
+If still unavailable: Web Search for official docs
+```
+
+## Installation
+
+If context7 is not installed, guide user:
+
+```bash
+/plugin install context7
+```