@fro.bot/systematic 1.23.2 → 2.0.0

package/skills/heal-skill/SKILL.md

@@ -1,148 +0,0 @@
----
-name: heal-skill
-description: Fix incorrect SKILL.md files when a skill has wrong instructions or outdated API references
-argument-hint: '[optional: specific issue to fix]'
-allowed-tools:
-  - Read
-  - Edit
-  - Bash(ls:*)
-  - Bash(git:*)
-disable-model-invocation: true
----
-
-<objective>
-Update a skill's SKILL.md and related files based on corrections discovered during execution.
-
-Analyze the conversation to detect which skill is running, reflect on what went wrong, propose specific fixes, get user approval, then apply changes with optional commit.
-</objective>
-
-<context>
-Skill detection: !`ls -1 ./skills/*/SKILL.md | head -5`
-</context>
-
-<quick_start>
-<workflow>
-1. **Detect skill** from conversation context (invocation messages, recent SKILL.md references)
-2. **Reflect** on what went wrong and how you discovered the fix
-3. **Present** proposed changes with before/after diffs
-4. **Get approval** before making any edits
-5. **Apply** changes and optionally commit
-</workflow>
-</quick_start>
-
-<process>
-<step_1 name="detect_skill">
-Identify the skill from conversation context:
-
-- Look for skill invocation messages
-- Check which SKILL.md was recently referenced
-- Examine current task context
-
-Set: `SKILL_NAME=[skill-name]` and `SKILL_DIR=./skills/$SKILL_NAME`
-
-If unclear, ask the user.
-</step_1>
-
-<step_2 name="reflection_and_analysis">
-Focus on $ARGUMENTS if provided, otherwise analyze broader context.
-
-Determine:
-- **What was wrong**: Quote specific sections from SKILL.md that are incorrect
-- **Discovery method**: Context7, error messages, trial and error, documentation lookup
-- **Root cause**: Outdated API, incorrect parameters, wrong endpoint, missing context
-- **Scope of impact**: Single section or multiple? Related files affected?
-- **Proposed fix**: Which files, which sections, before/after for each
-</step_2>
-
-<step_3 name="scan_affected_files">
-```bash
-ls -la $SKILL_DIR/
-ls -la $SKILL_DIR/references/ 2>/dev/null
-ls -la $SKILL_DIR/scripts/ 2>/dev/null
-```
-</step_3>
-
-<step_4 name="present_proposed_changes">
-Present changes in this format:
-
-```
-**Skill being healed:** [skill-name]
-**Issue discovered:** [1-2 sentence summary]
-**Root cause:** [brief explanation]
-
-**Files to be modified:**
-- [ ] SKILL.md
-- [ ] references/[file].md
-- [ ] scripts/[file].py
-
-**Proposed changes:**
-
-### Change 1: SKILL.md - [Section name]
-**Location:** Line [X] in SKILL.md
-
-**Current (incorrect):**
-```
-[exact text from current file]
-```
-
-**Corrected:**
-```
-[new text]
-```
-
-**Reason:** [why this fixes the issue]
-
-[repeat for each change across all files]
-
-**Impact assessment:**
-- Affects: [authentication/API endpoints/parameters/examples/etc.]
-
-**Verification:**
-These changes will prevent: [specific error that prompted this]
-```
-</step_4>
-
-<step_5 name="request_approval">
-```
-Should I apply these changes?
-
-1. Yes, apply and commit all changes
-2. Apply but don't commit (let me review first)
-3. Revise the changes (I'll provide feedback)
-4. Cancel (don't make changes)
-
-Choose (1-4):
-```
-
-**Wait for user response. Do not proceed without approval.**
-</step_5>
-
-<step_6 name="apply_changes">
-Only after approval (option 1 or 2):
-
-1. Use edit tool for each correction across all files
-2. Read back modified sections to verify
-3. If option 1, commit with structured message showing what was healed
-4. Confirm completion with file list
-</step_6>
-</process>
-
-<success_criteria>
-- Skill correctly detected from conversation context
-- All incorrect sections identified with before/after
-- User approved changes before application
-- All edits applied across SKILL.md and related files
-- Changes verified by reading back
-- Commit created if user chose option 1
-- Completion confirmed with file list
-</success_criteria>
-
-<verification>
-Before completing:
-
-- Read back each modified section to confirm changes applied
-- Ensure cross-file consistency (SKILL.md examples match references/)
-- Verify git commit created if option 1 was selected
-- Check no unintended files were modified
-</verification>
-

package/skills/resolve_parallel/SKILL.md

@@ -1,36 +0,0 @@
----
-name: resolve_parallel
-description: Resolve all TODO comments using parallel processing
-argument-hint: '[optional: specific TODO pattern or file]'
-disable-model-invocation: true
----
-
-Resolve all TODO comments using parallel processing.
-
-## Workflow
-
-### 1. Analyze
-
-Gather the things todo from above.
-
-### 2. Plan
-
-Create a todowrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.
-
-### 3. Implement (PARALLEL)
-
-Spawn a pr-comment-resolver agent for each unresolved item in parallel.
-
-So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
-
-1. task pr-comment-resolver(comment1)
-2. task pr-comment-resolver(comment2)
-3. task pr-comment-resolver(comment3)
-
-Always run all in parallel subagents/Tasks for each Todo item.
-
-### 4. Commit & Resolve
-
-- Commit changes
-- Push to remote
-

package/skills/resolve_todo_parallel/SKILL.md

@@ -1,38 +0,0 @@
----
-name: resolve_todo_parallel
-description: Resolve all pending CLI todos using parallel processing
-argument-hint: '[optional: specific todo ID or pattern]'
----
-
-Resolve all TODO comments using parallel processing.
-
-## Workflow
-
-### 1. Analyze
-
-Get all unresolved TODOs from the /todos/\*.md directory
-
-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 compound-engineering pipeline artifacts that are intentional and permanent.
-
-### 2. Plan
-
-Create a todowrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.
-
-### 3. Implement (PARALLEL)
-
-Spawn a pr-comment-resolver agent for each unresolved item in parallel.
-
-So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
-
-1. task pr-comment-resolver(comment1)
-2. task pr-comment-resolver(comment2)
-3. task pr-comment-resolver(comment3)
-
-Always run all in parallel subagents/Tasks for each Todo item.
-
-### 4. Commit & Resolve
-
-- Commit changes
-- Remove the TODO from the file, and mark it as resolved.
-- Push to remote
-