Audit money-touched code changes before merge and report severity-based findings.
npx skills add https://github.com/leocosta/octopus --skill audit-money
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
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.
Run the audit-money skill on a PR to generate a money-focused report before merging.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
a29paulDetects SQL injection, LLM trust boundary violations, race conditions, and enum gaps in pull request diffs.
sergicalParse Sentry bot comments in GitHub PRs to extract issues and suggested fixes.
michaelalberReview .NET applications for OWASP Top 10 vulnerabilities and Telerik CVEs.
chrisallenlaneIdentify and fix code quality issues through safe, incremental refactorings with QA validation.
