code-reviewer-general

Sub-skill of code-reviewer: General (+5).

5 stars

Best use case

code-reviewer-general is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of code-reviewer: General (+5).

Teams using code-reviewer-general should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/general/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/development/code-reviewer/general/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/general/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How code-reviewer-general Compares

Feature / Agentcode-reviewer-generalStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of code-reviewer: General (+5).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# General (+5)

## General


- [ ] Code compiles/builds without errors
- [ ] No merge conflicts
- [ ] Branch is up to date with target
- [ ] Commit messages are clear

## Functionality


- [ ] Requirements are met
- [ ] Edge cases handled
- [ ] Error handling is appropriate
- [ ] No regression in existing functionality

## Code Quality


- [ ] Follows project coding standards
- [ ] No code smells or anti-patterns
- [ ] Appropriate comments (not excessive)
- [ ] No dead code or debug statements

## Security


- [ ] No hardcoded secrets
- [ ] Input validation present
- [ ] Output encoding where needed
- [ ] Proper error messages (no info leak)

## Testing


- [ ] New code has tests
- [ ] All tests pass
- [ ] Test coverage adequate
- [ ] Tests are meaningful

## Documentation


- [ ] README updated if needed
- [ ] API docs updated if applicable
- [ ] Breaking changes documented