banking-domain-reviewer

Flag banking-domain code review issues violating double-entry accounting and compliance patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill banking-domain-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: banking-domain-reviewer
Source: https://github.com/firefly-oss/firefly-oss-claude-skills/tree/main/agents/banking-domain-reviewer
Command: npx skills add https://github.com/firefly-oss/firefly-oss-claude-skills --skill banking-domain-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that changes to the Firefly Banking Platform codebase adhere to double-entry accounting rules, banking-domain compliance requirements, and regulatory patterns to prevent financial inconsistencies and compliance gaps during development.

Core Features & Use Cases

  • Domain-aware review checks business flows, ledger integrity, and regulatory alignment within code changes.
  • Compliance & audit readiness surfaces issues related to internal controls, data handling, and traceability for banking operations.
  • Actionable feedback provides clear remediation steps aligned with banking-domain best practices and governance.

Quick Start

Review the attached pull request and return a prioritized checklist focusing on accounting integrity, compliance, and security implications.

Frequently Asked Questions about banking-domain-reviewer

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

FAQPage Schema
How do I review banking code for double-entry accounting and compliance violations?

Review banking code for double-entry accounting and compliance violations by applying repository patterns to flag structural integrity, data handling, and auditing risks across transactions, payments, and ledger interactions. This generates a structured risk report for developer guidance.

What is a banking domain code review for regulatory compliance?

A banking domain code review for regulatory compliance validates code changes against double-entry accounting rules, internal controls, and SCA-related flows. It surfaces traceability issues to ensure banking operations remain audit-ready and financially consistent.

How do I check a pull request for financial ledger integrity and security risks?

Check a pull request for financial ledger integrity and security risks by reviewing the attached changes and returning a prioritized checklist. This checklist focuses on accounting integrity, compliance gaps, and security implications to guide reviewers.

Can I use automated checks to ensure code changes adhere to banking compliance requirements?

Yes, you can use automated checks to ensure code changes adhere to banking compliance requirements. The review identifies business flow violations and regulatory misalignment, providing clear remediation steps aligned with governance best practices.

Does double-entry accounting code review cover SCA-related payment flows?

Yes, double-entry accounting code review covers SCA-related payment flows. The check evaluates transactional interactions and data handling across payments and ledgers, highlighting critical risks and improvement opportunities for secure banking platforms.