oracle-plus-join-rewriter

Rewrite Oracle legacy (+) and comma joins into ANSI JOIN syntax.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/SukiEva/AgentSkills --skill oracle-plus-join-rewriter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oracle-plus-join-rewriter
Source: https://github.com/SukiEva/AgentSkills/tree/main/skills/oracle-plus-join-rewriter
Command: npx skills add https://github.com/SukiEva/AgentSkills --skill oracle-plus-join-rewriter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rewrite Oracle legacy outer join syntax that uses (+) into standard ANSI JOIN SQL, and convert comma-style joins to explicit INNER JOIN when that can be proven not to change the result set, while preserving unchanged text outside the rewritten join-related clauses. Use when the user provides Oracle SQL containing (+), comma joins in FROM, wants a standards-compliant rewrite, wants only the necessary join-related edits, or needs a safety review for whether the rewrite could change the result set.

Core Features & Use Cases

  • Rewrites legacy Oracle outer joins that use (+) into ANSI JOIN syntax, clarifying join direction.
  • Converts safe comma-style inner joins to explicit INNER JOIN when the overall result set remains the same.
  • Preserves non-join text, aliases, hints, and the broader query structure while applying join-related edits.
  • Performs risk checks and flags cases that require business confirmation before finalizing changes.

Quick Start

Provide a sample Oracle SQL containing (+) or comma-style joins in FROM, and I will generate an ANSI JOIN version with minimal, join-focused edits.

Frequently Asked Questions about oracle-plus-join-rewriter

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

FAQPage Schema
How do I rewrite Oracle (+) outer join syntax to ANSI JOIN format?

To rewrite Oracle (+) outer join syntax, the tool identifies the join direction and converts the legacy Oracle SQL into standards-compliant ANSI JOIN syntax while preserving non-join text, aliases, and query structure.

When do I need to convert comma-style joins to explicit ANSI INNER JOIN?

You convert comma-style joins to explicit ANSI INNER JOIN when the tool can safely verify that the overall result set remains completely unchanged, ensuring the rewrite does not alter query behavior.

What is the safest way to migrate legacy Oracle SQL joins to ANSI standards?

The safest way to migrate Oracle joins involves applying minimal edits only to join-related clauses and performing risk checks to flag any conversion cases that require business confirmation before finalizing.

Does converting Oracle (+) joins preserve existing SQL hints and aliases?

Yes, converting Oracle (+) joins preserves existing SQL hints, table aliases, and the broader query structure by applying only the necessary join-focused edits and leaving non-join text untouched.

Why might an Oracle to ANSI join rewrite require business confirmation?

An Oracle to ANSI join rewrite requires business confirmation when risk checks identify that converting comma joins to INNER JOIN or translating (+) syntax may potentially change the result set.