Review logo

Review

Community
mochow13
review

Review current code changes for bugs, regressions, test gaps, and project-guideline violations.

Overview

Publishermochow13
Repositorykeen-code
Skill namereview
Stars
88
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mochow13 on GitHub. Read the source before you install it.

Installation

Install the Review AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mochow13/keen-code/tree/main/internal/skills/bundled/review
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mochow13/keen-code.git /tmp/keen-code
mkdir -p .claude/skills
cp -r /tmp/keen-code/internal/skills/bundled/review .claude/skills/review
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Review in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Review on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Review is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Review Skill

Review focus (optional): $ARGUMENTS

Steps

  1. Gather change context. Run in parallel:

    • git status --short
    • git diff --staged
    • git diff
    • git ls-files --others --exclude-standard
    • git log -n 3 --oneline

    Review both staged and unstaged changes. Treat untracked files as relevant when they appear related to the user's request, and open them directly because git diff will not show their contents.

  2. Read project conventions. If AGENTS.md, CLAUDE.md, or CONTRIBUTING.md exist at the repo root, read them before judging the diff.

  3. Inspect the changed code. Open the files and surrounding code needed to verify behavior. Do not rely only on the diff when control flow, data shape, or tests depend on nearby context.

  4. Review against these checks:

    Correctness

    • No behavior regressions, missed edge cases, or undefined references
    • Error handling matches the risk and existing project patterns
    • Public contracts, CLI behavior, file formats, and compatibility are preserved unless the user asked to change them
    • Imports, variables, or functions made unused by the changes are removed

    Surgical Changes

    • Every changed line traces to the user's request
    • No "improvements" to adjacent code, comments, or formatting
    • No refactored code that wasn't broken
    • No deleted pre-existing dead code unless explicitly asked

    Simplicity

    • No speculative features or abstractions
    • No unnecessary configurability
    • No error handling for impossible scenarios
    • Functions are as short as they can be while remaining clear

    Testing

    • Critical paths have tests
    • New functionality is exercised by tests
    • Existing tests still cover the changed behavior
    • Relevant tests pass, or any unrun tests are called out with the reason

    Style

    • Matches existing naming and patterns
    • Minimal comments (only when strictly necessary)
    • Language-specific formatting applied (e.g., gofmt)
  5. Report findings first.

    • Start with bugs, regressions, security issues, and missing critical tests.
    • Include precise file:line references for every finding.
    • Order findings by severity: blocker, warning, then nit.
    • Explain the impact and the smallest practical fix.
    • If there are no findings, say so clearly and mention any residual test risk.
  6. Do not apply fixes yourself. Present the review and let the user decide what to fix.

Output Format

Use this structure:

  1. Findings
  2. Open questions or assumptions
  3. Test coverage and commands run

Keep summaries brief. If there are no findings, the first line should state that no issues were found.

Frequently asked questions

What does the Review AI skill do?

Review current code changes for bugs, regressions, test gaps, and project-guideline violations.

Why use Review on TypingMind?

Because you install it once and use it with any model. Review is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Review in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mochow13/keen-code/tree/main/internal/skills/bundled/review. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Review?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Review?

As many as you like. As long as a model supports skills, you can use Review with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Review AI skill free?

Yes. It is published on GitHub by mochow13 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇