Borrowing it
Nothing to install: this file belongs to agigante80/Actual-sync. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agigante80/Actual-sync/main/.claude/commands/pr-enhance.mdgit clone --depth 1 https://github.com/agigante80/Actual-syncWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/agigante80/actual-sync/pr-enhance)<a href="https://agentmods.dev/commands/agigante80/actual-sync/pr-enhance"><img src="https://agentmods.dev/badge/commands/agigante80/actual-sync/pr-enhance.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.05896 |
| Opus 5 | $0.00000 | $0.02948 |
| Sonnet 5 | $0.00000 | $0.01179 |
| Haiku 4.5 | $0.00000 | $0.00590 |
Grade A, and why
pr-enhance scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
result = subprocess.run(cmd.split(), capture_output=True, text=True) How it starts
The opening of the file, as written. The whole thing — 756 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Enhancement
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability — tailored to the Actual-sync repository.
Context
The user needs to create or improve pull requests with detailed descriptions, proper documentation, test coverage analysis, and review facilitation. Focus on making PRs that are easy to review, well-documented, and include all necessary context.
Repository Context (Actual-sync)
Ground every recommendation in this repo's real setup:
- Host: GitHub — the
ghCLI works here. Repo slug:agigante80/Actual-sync. - Stack: a single plain Node.js service (Express,
better-sqlite3,@actual-app/api). No TypeScript, no bundler, no build step, and no linter or type-checker. Do not assume React/Spring/Django/Rails, Prisma, or monorepo packages — none exist. - Branch model:
developmentis the active integration branch;mainholds production-ready releases. Feature work lands ondevelopment, so open PRs againstdevelopmentand diff against it.- Never push to
maindirectly. Mergingdevelopment→mainhappens ONLY when the user explicitly asks ("merge to main"). - Do not run
git pushunless the user asked for it in that same message.
- Never push to
- Releases are automated: every successful CI run on
maintriggers.github/workflows/auto-release.yml, which tagsvX.Y.Zand publishes a Release. A routine patch is just mergingdevelopment→main(the bot patch-bumps). For a minor/major, runnpm run version:bump -- minor|majorondevelopmentfirst, then merge. A manual bump commit must NOT use thechore(release): bump versionprefix (that prefix is the bot's recursion guard) — usechore: bump version to X. - Validation the PR can claim (run these; there is no lint/typecheck/build to cite):
npm test— full Jest suite (includes the doc↔code drift guards and knip-config guard).npm run test:coverage— Jest coverage; thresholds are 61% branches / 70% functions / 70% lines / 70% statements. Notesrc/syncService.jsandindex.jsare excluded from coverage collection.npm run dead:check— knip dead-code check (blocking; CI runs it in the lint job).
- CI workflows live in
.github/workflows/(ci-cd.yml,codeql-analysis.yml,dependency-update.yml, and others). - Commit style: Conventional Commits, as in the repo history — e.g.
feat(dashboard): ...,chore(deps-dev): ...,fix(sync): .... Reference issues with#NN.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 756 lines · 0 tokens per session scan A 6993b67be7b2
pr-enhance is a command published in the GitHub repository agigante80/Actual-sync (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,896 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other commands, from other repositories
sync-pr-body
Bring the pull request description back in line with the code after correction rounds changed it. The description was written when the draft PR opened; corrections since then may have falsified specific claims in it. Your product is an accurate PR body — nothing else.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
auto-review.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure Ornek cikti.
mr-description-creator
Generate and apply MR/PR description directly via gh or glab CLI (project).
code-review
Code review — local uncommitted changes or GitHub PR (pass PR number/URL for PR mode).
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.