actual-mcp-server: Command for Claude Code

Pull Request Enhancement

You are a PR optimization expert for actual-mcp-server (repo: agigante80/actual-mcp-server). Generate comprehensive PR descriptions that facilitate efficient code reviews for the develop branch workflow.

Context

The user needs to create or improve a pull request. Focus on making PRs that are easy to review, well-documented, and include all necessary context for the actual-mcp-server project.

Requirements

$ARGUMENTS

Instructions

1. PR Analysis

Gather PR context:

# Current branch and base
git branch --show-current
git log --oneline develop...HEAD

# Changed files vs develop (not main — this project targets develop)
git diff --name-status develop...HEAD

# Change statistics
git diff --shortstat develop...HEAD

# Commits
git log develop...HEAD --pretty=format:"%h %s" | head -20

Categorize changed files:

• src/tools/*.ts → tool changes (note which tools added/modified)
• src/lib/actual-adapter.ts → critical adapter change (requires extra scrutiny)
• src/actualToolsManager.ts → tool registration change
• tests/** → test changes
• docs/**, *.md → documentation
• docker-compose*.yaml → Docker/infra
• package.json, tsconfig.json → config/dependency changes

2. Project-specific checks

Before writing the description, run the pre-merge validation sequence:

npm run build 2>&1 | tail -3
npm run verify-tools 2>&1 | tail -3
npm run test:unit-js 2>&1 | tail -5
npm audit --audit-level=moderate 2>&1 | tail -3

Note any failures prominently in the PR description.

3. PR Description

Generate a PR description using this template:

## Summary

[1-3 bullet points describing what this PR does and why]

## Changes

### Tools affected
[List tools added/modified, or "None — infrastructure change"]

### Files changed
- `src/tools/...` — [what changed]
- `tests/...` — [what tests added/updated]
- [other significant files]

## Type of change
- [ ] New MCP tool (requires: verify-tools count update, E2E test, docs sync)
- [ ] Bug fix (existing tool behaviour corrected)
- [ ] Enhancement (existing tool improved)
- [ ] Infrastructure / dependency update
- [ ] Documentation only

## Validation

Pre-merge checklist (run before requesting review):
- [ ] `npm run build` — TypeScript compiles cleanly
- [ ] `npm run verify-tools` — all N tools registered
- [ ] `npm run test:unit-js` — unit + schema tests pass
- [ ] `npm audit --audit-level=moderate` — no new vulnerabilities
- [ ] Amounts in integer cents (not decimal dollars) — verified
- [ ] Date fields as YYYY-MM-DD strings (not Date.now()) — verified
- [ ] withActualApi wraps every Actual API operation — verified

## Breaking changes
[None / describe any breaking changes to MCP tool contracts or env var names]

## Notes for reviewer
[Anything non-obvious: why withActualApi is used a certain way, why a certain approach was chosen, file safety tier of changed files]