@fro.bot/systematic 2.2.1 → 2.3.1

package/skills/resolve-pr-parallel/SKILL.md

@@ -1,96 +0,0 @@
----
-name: resolve-pr-parallel
-description: Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
-argument-hint: '[optional: PR number or current PR]'
-disable-model-invocation: true
-allowed-tools: Bash(gh *), Bash(git *), Read
----
-
-# Resolve PR Comments in Parallel
-
-Resolve all unresolved PR review comments by spawning parallel agents for each thread.
-
-## Context Detection
-
-Detect git context from the current working directory:
-- Current branch and associated PR
-- All PR comments and review threads
-- Works with any PR by specifying the number
-
-## Workflow
-
-### 1. Analyze
-
-Fetch unresolved review threads using the GraphQL script at [scripts/get-pr-comments](scripts/get-pr-comments):
-
-```bash
-bash scripts/get-pr-comments PR_NUMBER
-```
-
-This returns only **unresolved, non-outdated** threads with file paths, line numbers, and comment bodies.
-
-If the script fails, fall back to:
-```bash
-gh pr view PR_NUMBER --json reviews,comments
-gh api repos/{owner}/{repo}/pulls/PR_NUMBER/comments
-```
-
-### 2. Plan
-
-Create a task list of all unresolved items grouped by type (e.g., `todowrite` in OpenCode, `update_plan` in Codex):
-- Code changes requested
-- Questions to answer
-- Style/convention fixes
-- Test additions needed
-
-### 3. Implement (PARALLEL)
-
-Spawn a `systematic:workflow:pr-comment-resolver` agent for each unresolved item.
-
-If there are 3 comments, spawn 3 agents — one per comment. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially.
-
-Keep parent-context pressure bounded:
-- If there are 1-4 unresolved items, direct parallel returns are fine
-- If there are 5+ unresolved items, launch in batches of at most 4 agents at a time
-- Require each resolver agent to return a short status summary to the parent: comment/thread handled, files changed, tests run or skipped, any blocker that still needs human attention, and for question-only threads the substantive reply text so the parent can post or verify it
-
-If the PR is large enough that even batched short returns are likely to get noisy, use a per-run scratch directory such as `.context/systematic/resolve-pr-parallel/<run-id>/`:
-- Have each resolver write a compact artifact for its thread there
-- Return only a completion summary to the parent
-- Re-read only the artifacts that are needed to resolve threads, answer reviewer questions, or summarize the batch
-
-### 4. Commit & Resolve
-
-- Commit changes with a clear message referencing the PR feedback
-- Resolve each thread programmatically using [scripts/resolve-pr-thread](scripts/resolve-pr-thread):
-
-```bash
-bash scripts/resolve-pr-thread THREAD_ID
-```
-
-- Push to remote
-
-### 5. Verify
-
-Re-fetch comments to confirm all threads are resolved:
-
-```bash
-bash scripts/get-pr-comments PR_NUMBER
-```
-
-Should return an empty array `[]`. If threads remain, repeat from step 1.
-
-If a scratch directory was used and the user did not ask to inspect it, clean it up after verification succeeds.
-
-## Scripts
-
-- [scripts/get-pr-comments](scripts/get-pr-comments) - GraphQL query for unresolved review threads
-- [scripts/resolve-pr-thread](scripts/resolve-pr-thread) - GraphQL mutation to resolve a thread by ID
-
-## Success Criteria
-
-- All unresolved review threads addressed
-- Changes committed and pushed
-- Threads resolved via GraphQL (marked as resolved on GitHub)
-- Empty result from get-pr-comments on verify
-

package/skills/resolve-pr-parallel/scripts/get-pr-comments

@@ -1,68 +0,0 @@
-#!/usr/bin/env bash
-
-set -e
-
-if [ $# -lt 1 ]; then
-    echo "Usage: get-pr-comments PR_NUMBER [OWNER/REPO]"
-    echo "Example: get-pr-comments 123"
-    echo "Example: get-pr-comments 123 EveryInc/cora"
-    exit 1
-fi
-
-PR_NUMBER=$1
-
-if [ -n "$2" ]; then
-    OWNER=$(echo "$2" | cut -d/ -f1)
-    REPO=$(echo "$2" | cut -d/ -f2)
-else
-    OWNER=$(gh repo view --json owner -q .owner.login 2>/dev/null)
-    REPO=$(gh repo view --json name -q .name 2>/dev/null)
-fi
-
-if [ -z "$OWNER" ] || [ -z "$REPO" ]; then
-    echo "Error: Could not detect repository. Pass OWNER/REPO as second argument."
-    exit 1
-fi
-
-gh api graphql -f owner="$OWNER" -f repo="$REPO" -F pr="$PR_NUMBER" -f query='
-query FetchUnresolvedComments($owner: String!, $repo: String!, $pr: Int!) {
-  repository(owner: $owner, name: $repo) {
-    pullRequest(number: $pr) {
-      title
-      url
-      reviewThreads(first: 100) {
-        totalCount
-        edges {
-          node {
-            id
-            isResolved
-            isOutdated
-            isCollapsed
-            path
-            line
-            startLine
-            diffSide
-            comments(first: 100) {
-              totalCount
-              nodes {
-                id
-                author {
-                  login
-                }
-                body
-                createdAt
-                updatedAt
-                url
-                outdated
-              }
-            }
-          }
-        }
-        pageInfo {
-          hasNextPage
-          endCursor
-        }
-      }
-    }
-  }
-}' | jq '.data.repository.pullRequest.reviewThreads.edges | map(select(.node.isResolved == false and .node.isOutdated == false))'

package/skills/resolve-todo-parallel/SKILL.md

@@ -1,68 +0,0 @@
----
-name: resolve-todo-parallel
-description: Resolve all pending CLI todos using parallel processing, compound on lessons learned, then clean up completed todos.
-argument-hint: '[optional: specific todo ID or pattern]'
----
-
-Resolve all TODO comments using parallel processing, document lessons learned, then clean up completed todos.
-
-## Workflow
-
-### 1. Analyze
-
-Get all unresolved TODOs from `.context/systematic/todos/*.md` and legacy `todos/*.md`
-
-Residual actionable work may come from `ce:review-beta mode:autonomous` after its in-skill `safe_auto` pass. Treat those todos as normal unresolved work items; the review skill has already decided they should not be auto-fixed inline.
-
-If any todo recommends deleting, removing, or gitignoring files in `docs/brainstorms/`, `docs/plans/`, or `docs/solutions/`, skip it and mark it as `wont_fix`. These are systematic pipeline artifacts that are intentional and permanent.
-
-### 2. Plan
-
-Create a task list of all unresolved items grouped by type (e.g., `todowrite` in OpenCode, `update_plan` in Codex). Analyze dependencies and prioritize items that others depend on. For example, if a rename is needed, it must complete before dependent items. Output a mermaid flow diagram showing execution order — what can run in parallel, and what must run first.
-
-### 3. Implement (PARALLEL)
-
-Spawn a `systematic:workflow:pr-comment-resolver` agent for each unresolved item.
-
-If there are 3 items, spawn 3 agents — one per item. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially respecting the dependency order from step 2.
-
-Keep parent-context pressure bounded:
-- If there are 1-4 unresolved items, direct parallel returns are fine
-- If there are 5+ unresolved items, launch in batches of at most 4 agents at a time
-- Require each resolver agent to return only a short status summary to the parent: todo handled, files changed, tests run or skipped, and any blocker that still needs follow-up
-
-If the todo set is large enough that even batched short returns are likely to get noisy, use a per-run scratch directory such as `.context/systematic/resolve-todo-parallel/<run-id>/`:
-- Have each resolver write a compact artifact for its todo there
-- Return only a completion summary to the parent
-- Re-read only the artifacts that are needed to summarize outcomes, document learnings, or decide whether a todo is truly resolved
-
-### 4. Commit & Resolve
-
-- Commit changes
-- Remove the TODO from the file, and mark it as resolved.
-- Push to remote
-
-GATE: STOP. Verify that todos have been resolved and changes committed. Do NOT proceed to step 5 if no todos were resolved.
-
-### 5. Compound on Lessons Learned
-
-Load the `ce:compound` skill to document what was learned from resolving the todos.
-
-The todo resolutions often surface patterns, recurring issues, or architectural insights worth capturing. This step ensures that knowledge compounds rather than being lost.
-
-GATE: STOP. Verify that the compound skill produced a solution document in `docs/solutions/`. If no document was created (user declined or no non-trivial learnings), continue to step 6.
-
-### 6. Clean Up Completed Todos
-
-Search both `.context/systematic/todos/` and legacy `todos/` for files with `done`, `resolved`, or `complete` status, then delete them to keep the todo list clean and actionable.
-
-If a per-run scratch directory was created at `.context/systematic/resolve-todo-parallel/<run-id>/`, and the user did not ask to inspect it, delete that specific `<run-id>/` directory after todo cleanup succeeds. Do not delete any other `.context/` subdirectories.
-
-After cleanup, output a summary:
-
-```
-Todos resolved: [count]
-Lessons documented: [path to solution doc, or "skipped"]
-Todos cleaned up: [count deleted]
-```
-

package/skills/triage/SKILL.md

@@ -1,312 +0,0 @@
----
-name: triage
-description: Triage and categorize findings for the CLI todo system
-argument-hint: '[findings list or source type]'
-disable-model-invocation: true
----
-
-- First set the /model to Haiku
-- Then read all pending todos from `.context/systematic/todos/` and legacy `todos/` directories
-
-Present all findings, decisions, or issues here one by one for triage. The goal is to go through each item and decide whether to add it to the CLI todo system.
-
-**IMPORTANT: DO NOT CODE ANYTHING DURING TRIAGE!**
-
-This command is for:
-
-- Triaging code review findings
-- Processing security audit results
-- Reviewing performance analysis
-- Handling any other categorized findings that need tracking
-
-## Workflow
-
-### Step 1: Present Each Finding
-
-For each finding, present in this format:
-
-```
----
-Issue #X: [Brief Title]
-
-Severity: 🔴 P1 (CRITICAL) / 🟡 P2 (IMPORTANT) / 🔵 P3 (NICE-TO-HAVE)
-
-Category: [Security/Performance/Architecture/Bug/Feature/etc.]
-
-Description:
-[Detailed explanation of the issue or improvement]
-
-Location: [file_path:line_number]
-
-Problem Scenario:
-[Step by step what's wrong or could happen]
-
-Proposed Solution:
-[How to fix it]
-
-Estimated Effort: [Small (< 2 hours) / Medium (2-8 hours) / Large (> 8 hours)]
-
----
-Do you want to add this to the todo list?
-1. yes - create todo file
-2. next - skip this item
-3. custom - modify before creating
-```
-
-### Step 2: Handle User Decision
-
-**When user says "yes":**
-
-1. **Update existing todo file** (if it exists) or **Create new filename:**
-
-   If todo already exists (from code review):
-
-   - Rename file from `{id}-pending-{priority}-{desc}.md` → `{id}-ready-{priority}-{desc}.md`
-   - Update YAML frontmatter: `status: pending` → `status: ready`
-   - Keep issue_id, priority, and description unchanged
-
-   If creating new todo:
-
-   ```
-   {next_id}-ready-{priority}-{brief-description}.md
-   ```
-
-   Priority mapping:
-
-   - 🔴 P1 (CRITICAL) → `p1`
-   - 🟡 P2 (IMPORTANT) → `p2`
-   - 🔵 P3 (NICE-TO-HAVE) → `p3`
-
-   Example: `042-ready-p1-transaction-boundaries.md`
-
-2. **Update YAML frontmatter:**
-
-   ```yaml
-   ---
-   status: ready # IMPORTANT: Change from "pending" to "ready"
-   priority: p1 # or p2, p3 based on severity
-   issue_id: "042"
-   tags: [category, relevant-tags]
-   dependencies: []
-   ---
-   ```
-
-3. **Populate or update the file:**
-
-   ```yaml
-   # [Issue Title]
-
-   ## Problem Statement
-   [Description from finding]
-
-   ## Findings
-   - [Key discoveries]
-   - Location: [file_path:line_number]
-   - [Scenario details]
-
-   ## Proposed Solutions
-
-   ### Option 1: [Primary solution]
-   - **Pros**: [Benefits]
-   - **Cons**: [Drawbacks if any]
-   - **Effort**: [Small/Medium/Large]
-   - **Risk**: [Low/Medium/High]
-
-   ## Recommended Action
-   [Filled during triage - specific action plan]
-
-   ## Technical Details
-   - **Affected Files**: [List files]
-   - **Related Components**: [Components affected]
-   - **Database Changes**: [Yes/No - describe if yes]
-
-   ## Resources
-   - Original finding: [Source of this issue]
-   - Related issues: [If any]
-
-   ## Acceptance Criteria
-   - [ ] [Specific success criteria]
-   - [ ] Tests pass
-   - [ ] Code reviewed
-
-   ## Work Log
-
-   ### {date} - Approved for Work
-   **By:** Claude Triage System
-   **Actions:**
-   - Issue approved during triage session
-   - Status changed from pending → ready
-   - Ready to be picked up and worked on
-
-   **Learnings:**
-   - [Context and insights]
-
-   ## Notes
-   Source: Triage session on {date}
-   ```
-
-4. **Confirm approval:** "✅ Approved: `{new_filename}` (Issue #{issue_id}) - Status: **ready** → Ready to work on"
-
-**When user says "next":**
-
-- **Delete the todo file** - Remove it from its current location since it's not relevant
-- Skip to the next item
-- Track skipped items for summary
-
-**When user says "custom":**
-
-- Ask what to modify (priority, description, details)
-- Update the information
-- Present revised version
-- Ask again: yes/next/custom
-
-### Step 3: Continue Until All Processed
-
-- Process all items one by one
-- Track using todowrite for visibility
-- Don't wait for approval between items - keep moving
-
-### Step 4: Final Summary
-
-After all items processed:
-
-````markdown
-## Triage Complete
-
-**Total Items:** [X] **Todos Approved (ready):** [Y] **Skipped:** [Z]
-
-### Approved Todos (Ready for Work):
-
-- `042-ready-p1-transaction-boundaries.md` - Transaction boundary issue
-- `043-ready-p2-cache-optimization.md` - Cache performance improvement ...
-
-### Skipped Items (Deleted):
-
-- Item #5: [reason] - Removed
-- Item #12: [reason] - Removed
-
-### Summary of Changes Made:
-
-During triage, the following status updates occurred:
-
-- **Pending → Ready:** Filenames and frontmatter updated to reflect approved status
-- **Deleted:** Todo files for skipped findings removed
-- Each approved file now has `status: ready` in YAML frontmatter
-
-### Next Steps:
-
-1. View approved todos ready for work:
-   ```bash
-   ls .context/systematic/todos/*-ready-*.md todos/*-ready-*.md 2>/dev/null
-   ```
-````
-
-2. Start work on approved items:
-
-   ```bash
-   /resolve-todo-parallel  # Work on multiple approved items efficiently
-   ```
-
-3. Or pick individual items to work on
-
-4. As you work, update todo status:
-   - Ready → In Progress (in your local context as you work)
-   - In Progress → Complete (rename file: ready → complete, update frontmatter)
-
-```
-
-## Example Response Format
-
-```
-
----
-
-Issue #5: Missing Transaction Boundaries for Multi-Step Operations
-
-Severity: 🔴 P1 (CRITICAL)
-
-Category: Data Integrity / Security
-
-Description: The google_oauth2_connected callback in GoogleOauthCallbacks concern performs multiple database operations without transaction protection. If any step fails midway, the database is left in an inconsistent state.
-
-Location: app/controllers/concerns/google_oauth_callbacks.rb:13-50
-
-Problem Scenario:
-
-1. User.update succeeds (email changed)
-2. Account.save! fails (validation error)
-3. Result: User has changed email but no associated Account
-4. Next login attempt fails completely
-
-Operations Without Transaction:
-
-- User confirmation (line 13)
-- Waitlist removal (line 14)
-- User profile update (line 21-23)
-- Account creation (line 28-37)
-- Avatar attachment (line 39-45)
-- Journey creation (line 47)
-
-Proposed Solution: Wrap all operations in ApplicationRecord.transaction do ... end block
-
-Estimated Effort: Small (30 minutes)
-
----
-
-Do you want to add this to the todo list?
-
-1. yes - create todo file
-2. next - skip this item
-3. custom - modify before creating
-
-```
-
-## Important Implementation Details
-
-### Status Transitions During Triage
-
-**When "yes" is selected:**
-1. Rename file: `{id}-pending-{priority}-{desc}.md` → `{id}-ready-{priority}-{desc}.md`
-2. Update YAML frontmatter: `status: pending` → `status: ready`
-3. Update Work Log with triage approval entry
-4. Confirm: "✅ Approved: `{filename}` (Issue #{issue_id}) - Status: **ready**"
-
-**When "next" is selected:**
-1. Delete the todo file from its current location
-2. Skip to next item
-3. No file remains in the system
-
-### Progress Tracking
-
-Every time you present a todo as a header, include:
-- **Progress:** X/Y completed (e.g., "3/10 completed")
-- **Estimated time remaining:** Based on how quickly you're progressing
-- **Pacing:** Monitor time per finding and adjust estimate accordingly
-
-Example:
-```
-
-Progress: 3/10 completed | Estimated time: ~2 minutes remaining
-
-```
-
-### Do Not Code During Triage
-
-- ✅ Present findings
-- ✅ Make yes/next/custom decisions
-- ✅ Update todo files (rename, frontmatter, work log)
-- ❌ Do NOT implement fixes or write code
-- ❌ Do NOT add detailed implementation details
-- ❌ That's for /resolve-todo-parallel phase
-```
-
-When done give these options
-
-```markdown
-What would you like to do next?
-
-1. run /resolve-todo-parallel to resolve the todos
-2. commit the todos
-3. nothing, go chill
-```
-

package/skills/workflows-brainstorm/SKILL.md

@@ -1,11 +0,0 @@
----
-name: workflows:brainstorm
-description: '[DEPRECATED] Use /ce:brainstorm instead — renamed for clarity.'
-argument-hint: '[feature idea or problem to explore]'
-disable-model-invocation: true
----
-
-NOTE: /workflows:brainstorm is deprecated. Please use /ce:brainstorm instead. This alias will be removed in a future version.
-
-/ce:brainstorm $ARGUMENTS
-

package/skills/workflows-compound/SKILL.md

@@ -1,10 +0,0 @@
----
-name: workflows:compound
-description: '[DEPRECATED] Use /ce:compound instead — renamed for clarity.'
-argument-hint: '[optional: brief context about the fix]'
-disable-model-invocation: true
----
-
-NOTE: /workflows:compound is deprecated. Please use /ce:compound instead. This alias will be removed in a future version.
-
-/ce:compound $ARGUMENTS

package/skills/workflows-plan/SKILL.md

@@ -1,10 +0,0 @@
----
-name: workflows:plan
-description: '[DEPRECATED] Use /ce:plan instead — renamed for clarity.'
-argument-hint: '[feature description, bug report, or improvement idea]'
-disable-model-invocation: true
----
-
-NOTE: /workflows:plan is deprecated. Please use /ce:plan instead. This alias will be removed in a future version.
-
-/ce:plan $ARGUMENTS

package/skills/workflows-review/SKILL.md

@@ -1,10 +0,0 @@
----
-name: workflows:review
-description: '[DEPRECATED] Use /ce:review instead — renamed for clarity.'
-argument-hint: '[PR number, GitHub URL, branch name, or latest]'
-disable-model-invocation: true
----
-
-NOTE: /workflows:review is deprecated. Please use /ce:review instead. This alias will be removed in a future version.
-
-/ce:review $ARGUMENTS

package/skills/workflows-work/SKILL.md

@@ -1,10 +0,0 @@
----
-name: workflows:work
-description: '[DEPRECATED] Use /ce:work instead — renamed for clarity.'
-argument-hint: '[plan file, specification, or todo file path]'
-disable-model-invocation: true
----
-
-NOTE: /workflows:work is deprecated. Please use /ce:work instead. This alias will be removed in a future version.
-
-/ce:work $ARGUMENTS