mssql-postgresql-stored-program-migration-review

Annotate MSSQL stored programs with PostgreSQL comments and generate a Markdown gap report.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ke-kishimoto/asp-todos --skill mssql-postgresql-stored-program-migration-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mssql-postgresql-stored-program-migration-review
Source: https://github.com/ke-kishimoto/asp-todos/tree/main/.agents/skills/mssql-postgresql-stored-program-migration-review
Command: npx skills add https://github.com/ke-kishimoto/asp-todos --skill mssql-postgresql-stored-program-migration-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Annotate an MSSQL stored program by reusing useful comments from the matching PostgreSQL function to document intent, identify migration gaps, and preserve the original MSSQL source during the review.

Core Features & Use Cases

  • Inline comments MSSQL with PostgreSQL-context to reveal intent and differences.
  • Generate a Markdown migration gap report that highlights behavior-changing differences without modifying the PostgreSQL source.
  • Keep PostgreSQL sources intact; annotate MSSQL in place for audit and collaboration.

Quick Start

Review the attached MSSQL stored program against the matching PostgreSQL function and generate a gap report without modifying the PostgreSQL file.

Frequently Asked Questions about mssql-postgresql-stored-program-migration-review

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

FAQPage Schema
How do I identify stored procedure migration gaps when moving from MSSQL to PostgreSQL?

To identify MSSQL to PostgreSQL migration gaps, this Skill annotates MSSQL stored programs by reusing comments from matching PostgreSQL functions and generates a Markdown gap report detailing behavior-changing differences.

Can I review MSSQL stored procedures against PostgreSQL equivalents without modifying the PostgreSQL source?

Yes, you can review MSSQL stored procedures without modifying the PostgreSQL source. This Skill annotates MSSQL files in place and never modifies PostgreSQL sources during the gap analysis.

What is the best way to document behavior differences between MSSQL and PostgreSQL stored programs?

The best way to document behavior differences is generating a formal Markdown gap report under docs/. This report highlights behavior-changing differences by reusing PostgreSQL function comments to annotate the MSSQL source.

How do I annotate MSSQL stored programs with PostgreSQL context for an audit?

To annotate MSSQL stored programs for audit, this Skill reuses inline comments from the matching PostgreSQL function to document intent and differences, editing the MSSQL files in place while preserving the original PostgreSQL source.

Does this MSSQL to PostgreSQL migration review work if I only have the MSSQL source files?

No, this migration review applies when migrating MSSQL stored procedures that already have PostgreSQL equivalents. It requires the matching PostgreSQL function to extract contextual comments and identify behavior-changing gaps.

Where does the generated migration gap report get saved during the stored program review?

The migration gap report is saved as a separate Markdown file under the docs/ directory. This keeps the formal gap report detailing behavior-changing differences separate from the annotated MSSQL source files.