financial-audit

Compare documented financial formulas against code implementations to flag discrepancies.

1|Updated Jan 28, 2026

Search Tags:#documentation #audit #formulas #financial #drift #code-review #tests

Ready to run

npx skills add https://github.com/Benmore-Studio/Benmore-Meridian --skill financial-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: financial-audit
Source: https://github.com/Benmore-Studio/Benmore-Meridian/tree/main/skills/financial-audit
Command: npx skills add https://github.com/Benmore-Studio/Benmore-Meridian --skill financial-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically verify that documented financial formulas match their code implementations, catching drift between docs and code.

Core Features & Use Cases

Discovery of formulas documented in CLAUDE.md and mapping to code implementations.
Verification of variable mappings and arithmetic to ensure parity.
Production-ready audit reporting highlighting matches, drift, and discrepancies before releases.

Quick Start

Run the financial-audit workflow to compare docs against code and generate a report.

Frequently Asked Questions about financial-audit

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

FAQPage Schema

How do I audit financial formulas for code parity before a release?▼

To audit financial formulas for code parity, you compare documented calculations in CLAUDE.md against actual code implementations to identify discrepancies. This requires module documentation, a test suite covering financial calculations, and code references to map variables accurately.

What is formula drift in financial code implementations?▼

Formula drift in financial code occurs when documented calculations and code implementations become misaligned over time. Auditing for this drift involves verifying that variable mappings and arithmetic in the documentation exactly match the production code.

When should I run a financial formula audit?▼

You should run a financial formula audit during module audits, pricing changes, or pre-release checks where formula drift could arise. These checkpoints ensure documentation and code implementations maintain parity before critical updates reach production.

What do I need to verify financial calculations against documentation?▼

To verify financial calculations against documentation, you need module documentation in CLAUDE.md, a test suite covering financial calculations, and corresponding code references. These inputs allow the audit to map variables to implementations and generate a parity report.

Can I map financial variables to code implementations without a test suite?▼

Mapping financial variables to code implementations without a test suite is not supported by this audit workflow. A test suite covering financial calculations is explicitly required alongside CLAUDE.md documentation and code references to verify parity and flag discrepancies.