mirror of
https://github.com/Heretek-AI/awesome-opencode.git
synced 2026-11-09 10:19:34 -10:00
John SmithandClaude Opus 5.5
3a6d104fcf
- kind/topics: keyword first pass, then reviewed and corrected by hand for all 513 entries - compat: detected from npm packages, package.json and source (scripts/utils/compat.js). Plugins: 134 v2, 125 v1, 12 unverified; 13 entries the review loop marked V2 pin @opencode-ai/plugin 1.x, and ~20 loop V2 verdicts based only on the absence of V1 markers are V1 plugin functions in source - npm and path filled where verifiable (package repository matches the entry); 9 bogus npm values from install prose were not kept - 29 repo URLs updated to the renamed/transferred repository; xberg-io entries point at their live repos instead of the archived monorepo; lavi uses repo + path instead of a /tree/ URL - removed projects/opencode-sessions.yaml (same repo as plugins/opencode-sessions.yaml) - install: renamed to installation:, mojibake fixed, inline HTML links removed from two descriptions Co-Authored-By: Claude Opus 5.5 <[email protected]>
21 lines
1.4 KiB
YAML
21 lines
1.4 KiB
YAML
name: SuperSpec
|
|
repo: https://github.com/lbk-open/super-spec
|
|
tagline: Requirement or production alert in, reviewed pull request out - 20 skills, one SKILL.md source
|
|
description: "A toolkit of 20 Agent Skills that combines the engineering discipline of superpowers with the living spec lifecycle of OpenSpec, and adds the two things neither has: end-to-end workflows that carry a requirement, or a production alert, all the way to a reviewed pull request, and multi-repo orchestration that runs one headless agent per repository. Implementation is dispatched to parallel test-driven subagents; a review panel with distinct lenses (quality, spec and guardrail compliance, cross-module integration) then returns a severity-graded verdict and drives a bounded fix loop until the code is approved. Root-cause analysis is evidence-based rather than a guess: competing hypotheses are falsified against logs, traces, metrics, code and git history before any fix is written. Capability specs follow the OpenSpec directory convention, so a repository initialized by the OpenSpec CLI works as-is. Nothing is written into your project - the guardrails are read in place at runtime, and there is no CLI or state machine to install."
|
|
kind: skill
|
|
topics:
|
|
- workflow
|
|
- code-quality
|
|
compat: n/a
|
|
scope:
|
|
- global
|
|
- project
|
|
tags:
|
|
- skills
|
|
- workflow
|
|
- code-review
|
|
- tdd
|
|
- multi-agent
|
|
- openspec
|
|
- spec-driven
|