audit-money

Audit money-touched code changes before merge and report severity-based findings.

4|Updated Mar 21, 2026

Search Tags:#automation #security #audit #compliance #billing #code-review #money

Ready to run

npx skills add https://github.com/leocosta/octopus --skill audit-money

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-money
Source: https://github.com/leocosta/octopus/tree/main/skills/audit-money
Command: npx skills add https://github.com/leocosta/octopus --skill audit-money

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits money-touched changes in code before merge to catch monetary logic defects, ensure correct handling of billing data, and prevent policy gaps that could lead to financial risk or regulatory exposure.

Core Features & Use Cases

Pre-merge money-touched diff analysis using keyword heuristics to identify money-related changes.
Seven inspection families covering types, rounding, tests, env-var consistency, idempotency, webhook verification, and disclosure coupling.
Severity-scoped findings with actionable fixes and clear reporting to guide PR reviewers and developers.

Quick Start

Run the audit-money skill on a PR to generate a money-focused report before merging.

Frequently Asked Questions about audit-money

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit billing logic in a pull request before merging?▼

To audit billing logic before merging, run a pre-merge money-audit that diffs changes against a base branch, detects money-touched files via keyword heuristics, and generates a severity-based report with actionable fixes.

What does a pre-merge money audit check for in revenue-related code?▼

A pre-merge money audit checks revenue-related code using seven inspection families covering types, rounding, tests, env-var consistency, idempotency, webhook verification, and disclosure coupling to surface monetary logic defects.

How do I catch rounding or idempotency issues in billing changes?▼

Catch rounding or idempotency issues in billing changes by running automated inspections that scan money-touched diffs for type errors, rounding inconsistencies, and idempotency gaps, reporting each finding by severity.

When do I need to run a money-focused code review on my changes?▼

Run a money-focused code review when a pull request touches billing data or revenue logic, ensuring correct monetary handling and preventing policy gaps that lead to financial risk or regulatory exposure.

Can I integrate automated compliance checks into my code review workflow?▼

Integrate automated compliance checks into your code review workflow by running the audit before merge, which outputs a structured report with location, description, and suggested fixes to guide reviewers.

What are the limitations of keyword heuristics for detecting money-touched files?▼

Keyword heuristics for detecting money-touched files are limited to matching specific terms in code, meaning untagged or unusually named revenue logic may be missed without explicit keyword inclusion.