Generic Code Reviewer logo

Generic Code Reviewer

Community
travisjneuman
generic-code-reviewer

Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.

Overview

Publishertravisjneuman
Repository.claude
Skill namegeneric-code-reviewer
Stars
98
Forks
22
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • 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 travisjneuman on GitHub. Read the source before you install it.

Installation

Install the Generic Code Reviewer 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.
  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/travisjneuman/.claude.git /tmp/.claude
mkdir -p .claude/skills
cp -r /tmp/.claude/skills/generic-code-reviewer .claude/skills/generic-code-reviewer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Generic Code Reviewer 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 Generic Code Reviewer 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 Generic Code Reviewer 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.

Generic Code Reviewer

Review code against production quality standards. Adapts to any project's tech stack.

Full Standards: See Code Review Standards

CLAUDE.md Compliance

Always check the project's CLAUDE.md for specific rules.

Before ANY Commit:

  • Task file exists in tasks/[feature-name].md
  • All tests passing
  • Type checking passing (if TypeScript)
  • No console errors/warnings
  • Bundle size within limits

Tech Stack Detection

DetectionStackKey Checks
React in package.jsonReact/TSComponents, hooks, state
Next.js in package.jsonNext.jsSSR, API routes
NestJS in package.jsonNestJSGuards, DTOs, services
.html files, no buildVanillaSemantic HTML, minimal JS
.py filesPythonType hints, validation

P0 Issues (Block Merge)

Security - Frontend

  • Sanitize input (textContent, not innerHTML)
  • unknown type for external data
  • No exposed API keys
  • HTTPS for external requests

Security - Backend

  • Input validation on all endpoints
  • Auth on protected routes
  • Parameterized queries (no raw SQL)
  • Secrets in environment variables

Correctness

  • Logic errors that break functionality
  • Type errors in strict mode
  • Unhandled promise rejections

P1 Issues (Should Fix)

Performance

Project TypeTarget
Static site< 50KB (excluding media)
SPA/React< 100KB gzipped initial
Full-stack< 200KB gzipped initial

Animation:

  • GPU-accelerated only (transform, opacity)
  • 60fps target
  • Use requestAnimationFrame

Accessibility (WCAG AA)

  • Focus indicators on interactive elements
  • Keyboard navigation (Tab, Enter, Escape)
  • Color contrast >= 4.5:1
  • ARIA labels on icon-only buttons
  • Alt text for meaningful images
  • Semantic HTML structure

P2 Issues (Nice to Have)

Code Quality

  • DRY, Single Responsibility
  • No magic numbers/strings
  • Self-documenting code
  • Follow existing patterns
  • No commented-out/dead code

Review Output Format

Only report issues found (don't list empty categories):

Blocking Issues (P0):

  • [Only if found - security, correctness issues]

Should Fix (P1):

  • [Only if found - performance, accessibility issues]

Consider (P2):

  • [Only if found - code quality polish]

If no issues: "Code review passed. Ready to merge."

Judgment Calls

When user asks "Is this OK?", consider:

ContextStricterMore Lenient
EnvironmentProductionPrototype/POC
PathHot path, frequently executedOne-time setup, admin only
VisibilityPublic API, external interfaceInternal helper, private method
TimelineFeature completeActive iteration

Adjust severity accordingly. P0 security issues are never lenient.

Quick Checklist

Pre-Commit:

  • Tests pass
  • Type/lint pass
  • Build succeeds
  • No console errors

Before Merge:

  • All P0 issues resolved
  • P1 issues addressed or tracked
  • P2 issues noted for future

See Also

Frequently asked questions

What does the Generic Code Reviewer AI skill do?

Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.

Why use Generic Code Reviewer on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/travisjneuman/.claude/tree/master/skills/generic-code-reviewer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Generic Code Reviewer?

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 Generic Code Reviewer?

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

Is the Generic Code Reviewer AI skill free?

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

Related AI Skills

View all
mattpocock logo

Diagnosing Bugs

mattpocock
CommunityPopular

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

22.3K
264.4K
2 files
View
mattpocock logo

Implement

mattpocock
CommunityPopular

Implement a piece of work based on a spec or set of tickets.

22.3K
264.4K
1 files
View
mattpocock logo

Improve Codebase Architecture

mattpocock
CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

22.3K
264.4K
2 files
View
mattpocock logo

Prototype

mattpocock
CommunityPopular

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

22.3K
264.4K
3 files
View

Set up your own AI workspace now

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