Requesting Code Review logo

Requesting Code Review

Community
thiientv
requesting-code-review

Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.

Overview

Publisherthiientv
Repositorygodmode
Skill namerequesting-code-review
Stars
99
Forks
76
Bundled files
1
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

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

Installation

Install the Requesting Code 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/thiientv/godmode/tree/main/skills/requesting-code-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/thiientv/godmode.git /tmp/godmode
mkdir -p .claude/skills
cp -r /tmp/godmode/skills/requesting-code-review .claude/skills/requesting-code-review
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Requesting Code 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 Requesting Code 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 Requesting Code 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.

Requesting Code Review

Make review cheap to perform and hard to misunderstand.

Prepare the packet

  1. Pin the comparison point and list changed files.
  2. Link the originating request, design, plan, or acceptance criteria.
  3. Summarize the behavior change and deliberately out-of-scope work.
  4. List risky boundaries: data, permissions, concurrency, public API, migrations, performance, compatibility, and user-visible behavior.
  5. Attach focused test/build/runtime evidence with command and result.
  6. Name known limits and ask specific questions rather than “please review.”
  7. Attach or write a short observable behavior contract for user-facing, CLI, API, generated-artifact, or operational changes. Keep it independent of the implementation so a reviewer can request source-blind validation.

Use review-request.md for the packet shape.

Reviewer selection

Ask for an independent pass when the change is public, risky, cross-cutting, security-sensitive, or difficult for its author to judge. Split contract and engineering-risk passes when independent agents are available. Keep the review scope large enough to include direct consumers but not unrelated cleanup.

Do not use a green test suite as a substitute for review, and do not present a review request as evidence that the change is correct. Pair source-aware review with behavior-validation when the change has a runnable public surface; a clean diff review cannot prove that surface works.

Completion condition

The request is ready when a reviewer can locate the contract, boundary, diff, evidence, and highest-risk questions without reconstructing author intent.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Requesting Code Review AI skill do?

Prepares a focused code review request for a branch, commit, pull request, or substantial working-tree diff by defining the review boundary, contract, risk areas, evidence, and questions for an independent reviewer. Use before merge or when another agent needs to review an implementation. Not for processing feedback already received or for claiming runtime correctness.

Why use Requesting Code Review on TypingMind?

Because you install it once and use it with any model. Requesting Code 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 Requesting Code Review in TypingMind?

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

Which AI models can use Requesting Code 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 Requesting Code Review?

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

Is the Requesting Code Review AI skill free?

Yes. It is published on GitHub by thiientv 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 👇