CodexPluginStats
← Plugin catalog
Developer Tools

VibeDoctor

VibeDoctor v1.0.0

Code health for your projects

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read a project's code health and open findings
  • Check code for security, dependency, quality and performance issues
  • Map the codebase: modules, callers, change impact, test coverage

Cost & access

This plugin does not sell products or process payments.

Declared limitations

  • Scanning a site the user does not own
  • Deleting findings
  • A project outside the connected account

Onboarding example

What are the most serious issues in my project?

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 6, 2026. Package observed Nov 5, 2026.

View package source →

Description

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.

ChatGPT marketplace listing ↗Website ↗Privacy policy ↗Terms ↗Support ↗

Matches for “codebase”

Exact text from the indicated source. A mention alone does not establish support for your task.

Publisher capabilities · listing

Read a project's code health and open findings Check code for security, dependency, quality and performance issues Map the codebase: modules, callers, change impact, test coverage Answer questions about the code's structure and health Record notes on findings

Publisher description

Code health for your VibeDoctor projects: findings from scans, checks of code you send, and a map of the codebase.

Publisher full description

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.

What changed

Keywords

Files & skills

File archives

Plugin package8 files · 33.6 KBBrowse files →
Skill instructions
check-changes825 Bytes

View saved version →

---
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.
get-started945 Bytes

View saved version →

---
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`.

Release notes

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.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Proprietary
Package author
VibeDoctor
Keywords
See keywords
Getting started skill
./skills/get-started/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Read a project's code health and open findings
  • Check code for security, dependency, quality and performance issues
  • Map the codebase: modules, callers, change impact, test coverage
  • Answer questions about the code's structure and health
  • Record notes on findings

Package observed Nov 5, 2026.

plugin.json
Technical details
First seen
Oct 24, 2026 · 12:40 UTC
Last seen
Nov 6, 2026 · 00:00 UTC
Collection status
Collected

plugin_asdk_app_6ad4830c0c0081919d71ae14e5bf7b5f

Download plugin data (JSON)