VibeDoctor v1.0.0
Code health for your projects
Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
From the marketplace listing
VibeDoctor scans your GitHub repositories and websites and keeps a record of each project's code health. Connect it to see a project's scores and open findings, check code for security, dependency, quality and performance issues, explore a map of the codebase (what a function touches, what a change affects, which parts have no tests), and record why a finding is a false positive. It works with the projects in your VibeDoctor account; you sign in once and choose Allow.
Language: English · Automatically detected from descriptions.
Oct 27, 2026 · 1 saved observations
Metadata · Oct 27, 2026 · 00:54 UTC · Compared with Oct 24, 2026 · 13:51 UTC
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Oct 24, 2026 · 13:51 UTC
Not present
Oct 27, 2026 · 00:54 UTC
false
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 2, 2026.
Review scenarios; not an exhaustive list.
This plugin does not sell products or process payments.
Terms may have changed since this observation.
--- name: check-changes description: Check the files changed in the current repository with VibeDoctor before a commit. Use when the user asks to check, review or validate their changes. --- # Check changed files with VibeDoctor 1. List the changed files: `git status --porcelain` (staged and unstaged), skipping deleted files, lockfiles and binaries. 2. Read each file's full content. Send up to 50 files per call to `vibedoctor_check`, each with its repository-relative path. Pass `project` as the repository's `owner/name` from `git remote get-url origin`. 3. Report the findings grouped by file, most severe first, with line numbers and the suggested fix. Say plainly when nothing was found. 4. If the user says a finding is wrong, record why with `vibedoctor_note`. Only the user can dismiss a finding, in VibeDoctor.
--- name: get-started description: Show the user their VibeDoctor projects and the health of one of them. Use when the user first connects VibeDoctor or asks how their project is doing. --- # Get started with VibeDoctor 1. Call `vibedoctor_projects` to see the projects this account can use. 2. If there are none, tell the user to add a GitHub repository or website at https://app.vibedoctor.io and come back after its first scan finishes. 3. If there are several, ask which one, unless the conversation already names a repository. In a code checkout, `git remote get-url origin` names it. 4. Call `vibedoctor_status` with that project. Summarize in plain words: the overall score, how many critical and high findings are open, and the two or three files that need attention first. Use only what the tool returned. 5. Offer what can come next: checking changed files with `vibedoctor_check`, or exploring the code map with `vibedoctor_graph`.
First release: project health, code checks, the code map, codebase questions and notes on findings.
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 2, 2026.
plugin_asdk_app_6ad4830c0c0081919d71ae14e5bf7b5f
Download plugin data (JSON)