opencode-plusplus
Reduces risky autonomous code changes by adding verification gates, impact analysis, and repair loops—critical for maintaining stability in production codeba…
OpenCode++: a Coding Agent Reliability Harness for OpenCode, adding context, edit boundaries, command evidence, verification gates, impact analysis, and repair loops.OpenCode++:面向 OpenCode 的 AI 编程可靠性增强框架,为其增加上下文管理、编辑边界、命令证据、验证门禁、影响分析与修复闭环能力。
- Ask Claude to verify code changes before applying them to prevent breaking existing functionality.
- Generate impact analysis reports showing which code sections are affected by proposed modifications.
- Automate repair loops to detect and fix errors in generated code automatically without manual intervention.
Reduces risky autonomous code changes by adding verification gates, impact analysis, and repair loops—critical for maintaining stability in production codebases where AI-generated edits can introduce hidden defects.
Engineering teams using OpenCode agents who need guardrails against unintended code mutations and cascading failures.
https://github.com/whut09/opencode-plusplus
By whut09
How to Get It
claude plugins install whut09/opencode-plusplus
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Verify code changes before applying them to prevent breaking existing functionality
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 109 GitHub stars; contributors unknown; last commit 0d ago; license no license.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 109 GitHub stars; contributors unknown; last commit 0d ago; license no license.