self-reviewing-code | aug-dev | ClaudePluginHub

Skill

Community

self-reviewing-code

0

Description

Self-review checklist before marking PR ready - catch clarity, correctness, and maintainability issues with fresh eyes

Install

1

Add the repository(one-time)

$

/plugin marketplace add bryonjacob/aug

2

Install the plugin

$

/plugin install aug-dev@aug

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Skill Content

Self-Reviewing Code

Purpose

Review your own PR with beginner-mind before marking ready. Step back and catch assumptions, missing edge cases, unclear code.

Core insight: You're too close to the code. Review as if seeing it for the first time.

Pre-Review

just check-all    # Automated checks
gh pr checks      # CI status

Self-Review Checklist

Before marking ready:

Software Laws

Apply these industry-standard principles:

Postel's Law - Liberal input acceptance, conservative output
Hyrum's Law - All observable behavior becomes API contract
Kernighan's Law - Simple code over clever code
Leaky Abstractions - Understand when abstractions leak
DRY - Single source of truth, no duplication
YAGNI - Add only when actually needed

Review Questions

Clarity:

Would this make sense to someone unfamiliar?
Variable/function names descriptive?
Complex logic commented with "why"?

Correctness:

Tests cover edge cases?
Error conditions handled?
Could this fail in production?

Maintainability:

Code DRY?
Functions single-responsibility?
Future changes easy?

Performance:

Obvious performance issues?
Database queries efficient?

Security:

Inputs validated?
Sensitive data handled properly?
No injection vulnerabilities?

Common Issues

Leftover debugging code (console.log, print)
Commented-out code
TODOs that should be issues
Magic numbers without constants
Missing null/undefined checks
Hardcoded values that should be config

Fresh Eyes Technique

Walk away 15+ minutes
Come back, review as if someone else wrote it
Read diff line by line
Question every decision

Ask: "Would I approve this reviewing someone else's code?"

Links

GitHub Stats

0 forks

Updated 1 month ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

47.1k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

47.1k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

47.1k