
Kodevu
Run AI-powered reviews on Git or SVN diffs from the terminal without wiring a custom review pipeline.
Overview
Kodevu is an agent skill for the Ship phase that fetches Git or SVN diffs and produces AI-generated code review reports via the kodevu CLI.
Install
npx skills add https://github.com/gyteng/kodevu --skill kodevuWhat is this skill?
- Reviews latest commit, a hash, last N commits, or uncommitted working tree via npx kodevu
- Routes diffs to AI backends: auto, openai, gemini, codex, or copilot with optional API keys and models
- Writes Markdown or JSON reports under ~/.kodevu or a custom --output directory
- Optional ~/.kodevu/config.json for settings that persist across sessions
- Custom --prompt to steer reviewers (e.g. security-focused passes)
- 5 reviewer backends: auto, openai, gemini, codex, copilot
Adoption & trust: 1 installs on skills.sh; 1/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You have local or recent VCS changes but no repeatable way to get consistent AI review output before you merge.
Who is it for?
Indie developers who already use git or svn locally and want one npx command to batch-review commits with their preferred AI CLI.
Skip if: Teams that need in-IDE inline review only, or repos where diffs must never leave the machine without a self-hosted reviewer you configure separately.
When should I use this skill?
When you need to fetch Git/SVN diffs and generate AI review reports with npx kodevu.
What do I get? / Deliverables
You get Markdown or JSON review artifacts for chosen revisions so you can fix issues or attach reports to PR discussion.
- Markdown or JSON review report files
- Configurable output directory and optional persistent ~/.kodevu/config.json
Recommended Skills
Journey fit
How it compares
Use instead of manually copying diffs into chat for every commit when you want saved, repeatable review files.
Common Questions / FAQ
Who is kodevu for?
Solo and small-team builders who ship from Git or SVN and want agent-guided runs of the kodevu CLI for commit or uncommitted diff reviews.
When should I use kodevu?
Use it in Ship (review) before merging—after your last commits, on a specific hash, on the last N commits, or on uncommitted changes when you want a report file.
Is kodevu safe to install?
The skill documents sending diffs to external AI reviewer CLIs; review the Security Audits panel on this page and treat API keys and diff content according to your repo policy.
SKILL.md
READMESKILL.md - Kodevu
# Kodevu Skill Kodevu is a Node.js tool that fetches Git commits or SVN revisions, sends the diff to a supported AI reviewer CLI, and writes review results to report files. It supports an optional persistent config file at `~/.kodevu/config.json` for settings that should survive across sessions. ## Usage Use `npx kodevu` to review a codebase. ### Reviewing the latest commit ```bash npx kodevu . ``` ### Reviewing a specific commit ```bash npx kodevu . --rev <commit-hash> ``` ### Reviewing the last N commits ```bash npx kodevu . --last 3 ``` ### Reviewing uncommitted changes ```bash npx kodevu . --uncommitted ``` ### Supported Reviewers `kodevu` supports several AI reviewer backends: `auto`, `openai`, `gemini`, `codex`, `copilot`. The default is `auto`, which probes available CLI tools in your `PATH`. Example using OpenAI: ```bash npx kodevu . --reviewer openai --openai-api-key <YOUR_API_KEY> --openai-model gpt-5-mini ``` ### Generating JSON Reports By default, review reports are generated as Markdown files in `~/.kodevu/`. You can specify `--format json` or change the output directory using `--output <dir>`. ```bash npx kodevu . --format json --output ./reports ``` ### Custom Prompts You can provide additional instructions to the reviewer using `--prompt`: ```bash npx kodevu . --prompt "Focus on security issues and suggest optimizations." ``` Or from a file: `--prompt @my-rules.txt` ### Environment Variables All options can also be set via environment variables to avoid repetitive flags: - `KODEVU_REVIEWER` – Default reviewer. - `KODEVU_LANG` – Default output language. - `KODEVU_OUTPUT_DIR` – Default output directory. - `KODEVU_PROMPT` – Default prompt instructions. - `KODEVU_OPENAI_API_KEY` – API key for `openai`. - `KODEVU_OPENAI_BASE_URL` – Base URL for `openai`. - `KODEVU_OPENAI_MODEL` – Model for `openai`. ### Configuration File For persistent settings that survive across shells and AI tool invocations, create `~/.kodevu/config.json`: ```json { "reviewer": "openai", "openaiApiKey": "sk-...", "openaiBaseUrl": "https://your-gateway.example.com/v1", "openaiModel": "gpt-4o", "lang": "zh" } ``` The file is optional and silently ignored if absent. Priority: **CLI flags > ENV vars > config file > defaults**. ## Working with Target Repositories - **Git**: `target` must be a local repository or subdirectory. - **SVN**: `target` can be a working copy path or repository URL. ```bash npx kodevu /path/to/project --last 1 ``` name: Publish to npm on: push: branches: - main workflow_dispatch: env: FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true jobs: publish: if: github.ref == 'refs/heads/main' runs-on: ubuntu-latest permissions: contents: read steps: - name: Checkout uses: actions/checkout@v6 - name: Setup Node.js uses: actions/setup-node@v6 with: node-version: 20 registry-url: https://registry.npmjs.org cache: npm - name: Install dependencies run: npm ci - name: Verify package run: npm run check - name: Check published version id: version_check shell: bash run: | PACKAGE_NAME=$(node -p "require('./package.json').name") PACKAGE_VERSION=$(node -p "require('./package.json').version") PUBLISHED_VERSION=$(npm view "$PACKAGE_NAME" version 2>/dev/null || true) echo "package_name=$PACKAGE_NAME" >> "$GITHUB_OUTPUT" echo "package_version=$PACKAGE_VERSION" >> "$GITHUB_OUTPUT" if [ -z "$PUBLISHED_VERSION" ]; then echo "should_publish=true" >> "$GITHUB_OUTPUT" exit 0 fi echo "published_version=$PUBLISHED_VERSION" >> "$GITHUB_OUTPUT" if node -e "const next=process.argv[1]; const current=process