mssql-stored-procedures

Enforce MSSQL stored procedure standards for banking applications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jamesbondev/ai-dotfiles --skill mssql-stored-procedures-jamesbondev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mssql-stored-procedures
Source: https://github.com/jamesbondev/ai-dotfiles/tree/main/.github/skills/mssql-stored-procedures
Command: npx skills add https://github.com/jamesbondev/ai-dotfiles --skill mssql-stored-procedures-jamesbondev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces rigorous standards for writing, reviewing, and debugging Microsoft SQL Server stored procedures, ensuring data integrity, financial precision, and security in banking applications.

Core Features & Use Cases

  • Standards Enforcement: Provides a comprehensive checklist and template for writing secure, efficient, and maintainable T-SQL code.
  • Data Integrity & Security: Highlights critical rules for transactions, SQL injection prevention, and error handling.
  • Financial Precision: Mandates correct data types (DECIMAL(19,4)) for monetary values and outlines rounding rules.
  • Use Case: When reviewing a new stored procedure for a fund transfer, use this Skill to ensure it adheres to all hard rules regarding transactions, parameter sniffing, and financial data types.

Quick Start

Use the mssql-stored-procedures skill to review the attached T-SQL script for potential data integrity risks.

Frequently Asked Questions about mssql-stored-procedures

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

FAQPage Schema
How do I enforce data integrity in MSSQL stored procedures for banking applications?

To enforce data integrity in MSSQL stored procedures, apply strict standards for transactions, error handling, and security. This prevents common bugs and vulnerabilities while ensuring financial precision in banking applications.

What is the correct data type for monetary values in T-SQL stored procedures?

The correct data type for monetary values in T-SQL is DECIMAL(19,4). Using this exact precision prevents calculation errors and ensures financial precision across banking applications.

How do I review a T-SQL script for SQL injection vulnerabilities and transaction risks?

Reviewing a T-SQL script for vulnerabilities involves checking against a comprehensive standards checklist for SQL injection prevention, transaction handling, and parameter sniffing to ensure secure execution.

Does this MSSQL stored procedure standard cover SQL performance issues and schema changes?

Yes, these MSSQL stored procedure standards cover SQL performance issues and schema changes. They provide specific rules for debugging and managing structural updates while maintaining data integrity.

Why does my banking stored procedure fail financial precision checks during code review?

Banking stored procedures fail financial precision checks when they use incorrect data types for monetary values. Enforcing DECIMAL(19,4) and strict rounding rules resolves these discrepancies.