claude

probe

Request Probe reviews, read findings, manage the review context and fix issues from Claude Code

1 on GitHubby Probe contributorsv0.2.0AGPL-3.0-onlyupdated 1 month ago
/

Plugin probe from marketplace probe in gvinsot/Probe. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (6)

  • context

    Manage what Probe reviews against — the base branch, the intent and acceptance criteria of the change, the pre-change plan, and the team's trusted policy and knowledge base. Use when the user wants to set or show the review context, record the task's acceptance criteria, or make a plan before coding

  • findings

    Read the findings of the latest Probe report — list them, filter them by severity or path, or show one in detail with its signals, evidence or check output. Use when the user asks what Probe found, about a finding id such as T3, or before fixing a finding.

  • fix

    Work on a Probe finding — understand it, change the code when a change is warranted, and check with Probe that the finding is resolved. Use when the user asks to fix a Probe finding such as T3, or all high-severity findings.

  • graph

    Explore the Probe repository graph of the current commit — components, packages, files, functions, types and external dependencies, with their calls, imports, dependencies and interface implementations — to see what a change affects beyond the diff. Use when the user asks who calls or depends on som

  • review

    Run Probe on the committed changes of the current branch and present its findings — reproduced issues, unresolved hypotheses, incomplete checks and the prioritized review targets. Use when the user asks for a Probe review, before handing over a committed change, or before opening a pull request.

  • setup

    Get Probe ready in the current repository — check the probe binary, create and commit the trusted .probe.json policy, prepare the sandbox image for full reviews, and optionally configure an AI provider. Use when Probe is not installed, when the repository has no .probe.json, or when the user asks to

Subagents (1)

  • probe-reviewer

    Runs Probe on the committed changes of the current branch and returns a short, categorized handoff — reproduced issues, divergences, unresolved hypotheses, incomplete checks and the top review targets — without loading the full report into the main conversation. Use proactively before handing over a

View source on GitHub probe.technology

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

ecc

claudecodex

Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses

200 skills · 98 commands · 71 agents · 1 MCP server · hooks

affaan-m/ECC 302,088

Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives

1 command

anthropics/claude-code 155,476

Tenant-isolated AI teams that plan work, coordinate tasks, recall approved context, and return evidence-backed results

6 skills · 6 commands · 4 agents · 1 MCP server

ruvnet/ruflo 81,589

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.

13 skills · 9 commands · 1 MCP server

anthropics/claude-plugins-official 47,076

Maintain probe?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted