github-pr-reviewer-aimemo

GitHub PR Reviewer with aimemo Memory

This skill reviews GitHub Pull Requests and learns your code style preferences over time using aimemo's persistent memory.

How It Works

1. Loads learned preferences from previous sessions
2. Reviews PR applying your established code style rules
3. Stores new patterns discovered during review
4. Remembers feedback you provide for future reviews

Memory Integration

CRITICAL: This skill uses aimemo for persistent memory. Always pass context: "github-pr-reviewer-aimemo" to all memory tool calls.

On Session Start

ALWAYS call memory_context FIRST before reviewing:
{
  "context": "github-pr-reviewer-aimemo"
}

This loads:

• Code style preferences
• Common patterns to watch for
• Previous feedback and corrections
• In-progress review tasks

During Review

Store discoveries immediately:

{
  "context": "github-pr-reviewer-aimemo",
  "entities": [{
    "name": "code-style-preferences",
    "entityType": "preferences",
    "observations": ["New pattern you discovered"]
  }]
}

On Session End

Write a journal entry:

{
  "context": "github-pr-reviewer-aimemo",
  "journal": "Reviewed PR #123. Updated: variable naming rules. Next: discuss error handling patterns with user."
}

Instructions

When the user asks you to review a GitHub PR:

Step 1: Load Memory (MANDATORY)

Before doing ANYTHING else, call:

memory_context({
  "context": "github-pr-reviewer-aimemo"
})

This gives you access to:

• User's code style preferences
• Previously identified anti-patterns
• Ongoing review tasks
• Past user feedback

Step 2: Fetch PR Details

Use GitHub API or ask user for PR link. Retrieve:

• PR title and description
• Changed files and diffs
• Existing review comments
• PR metadata (author, labels, etc.)

Step 3: Review Code

Apply learned preferences from memory:

Code Style:

• Check naming conventions (snake_case, camelCase, etc.)
• Verify indentation and formatting
• Look for trailing commas, semicolons based on preferences