← 输入框|github.com|刷新
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: microsoft/microsoft-sql
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: microsoft/microsoft-sql
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: rename-plugin-microsoft-sql
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 14 commits
  • 215 files changed
  • 1 contributor

Commits on Sep 18, 2026

  1. Rename the plugin to microsoft@microsoft-sql, shown as Microsoft SQL

    The install becomes `plugin add microsoft@microsoft-sql`: the plugin name is
    microsoft and the marketplace name is microsoft-sql, so generate.mjs now keeps
    them as two constants instead of one. The display name is Microsoft SQL,
    written to every manifest that has a display field, and now also to the
    marketplace entry, where Claude Code and Cursor read it.
    
    Repository links point at github.com/microsoft/microsoft-sql. They do not
    resolve until the repository is renamed, so this merges right after the rename.
    
    The README's Claude Code command installed azure-sql-skills@azure-sql-skills,
    a name no manifest ever declared. It now installs microsoft@microsoft-sql, and
    the Codex commands are added beside it.
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    a8d1977 View commit details
    Browse the repository at this point in the history
  2. Publish as Microsoft SQL everywhere, and add the Grok marketplace

    The author on every manifest is now Microsoft SQL, the description leads with
    Microsoft SQL, and microsoft-sql is the first keyword.
    
    Grok Build installs from .grok-plugin/marketplace.json, which this repository
    stopped generating in PR #9, so `grok plugin install microsoft` had nothing to
    read. It is generated again, in the source format Grok documents. AGENTS.md
    listed .grok-plugin/ and .agents/plugins/ as generated when neither was; it now
    names what the generator writes.
    
    Cursor honours displayName now. It showed Microsoft SQL for this plugin, so the
    comment claiming it ignores the field is replaced with that measurement.
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    d6c6443 View commit details
    Browse the repository at this point in the history
  3. Name the plugin Microsoft SQL, not a skill collection

    Microsoft SQL is the plugin's brand, and the plugin will carry an MCP server
    beside the skills, so no plugin-level name says skills any more: the README
    and llms.txt title, the description, package.json, and the install, badge and
    support links now use Microsoft SQL and microsoft/microsoft-sql.
    
    The skills themselves are unchanged. Each one is about Azure SQL Database and
    keeps that in its name and text.
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    aab18c2 View commit details
    Browse the repository at this point in the history
  4. Rewrite the plugin description around what an agent gains

    Leads with who publishes it, says what a coding agent learns rather than what
    it gets wrong, ends the range on a whole app built with Azure Functions and
    Azure SQL Database, and keeps the live-database testing as the proof.
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    1cfeb8f View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    a37e159 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    1ee4187 View commit details
    Browse the repository at this point in the history
  7. Describe the plugin by what you build with it

    Build AI-ready apps on Azure SQL Database, then the concrete pieces the plugin
    covers today: vector search, RAG, REST APIs, serverless functions, passwordless
    auth and ORMs. The pattern Neon's and Supabase's plugins use: concrete
    capabilities rather than a sentence about behaviour.
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    b0d4328 View commit details
    Browse the repository at this point in the history
  8. Add the GitHub Copilot CLI install commands to the README

    Tested from this branch: the marketplace registers as microsoft-sql and the
    plugin installs all 57 skills into ~/.copilot/installed-plugins, the folder
    Visual Studio Code also loads from.
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    0dd9e16 View commit details
    Browse the repository at this point in the history
  9. Merge remote-tracking branch 'origin/main' into rename-plugin-microso…

    …ft-sql
    
    # Conflicts:
    #	llms.txt
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    8dffca7 View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    73e630e View commit details
    Browse the repository at this point in the history
  11. Merge remote-tracking branch 'origin/main' into rename-plugin-microso…

    …ft-sql
    
    # Conflicts:
    #	llms.txt
    croblesm committed Sep 18, 2026
    Configuration menu
    Copy the full SHA
    20ecdf6 View commit details
    Browse the repository at this point in the history

Commits on Sep 19, 2026

  1. Configuration menu
    Copy the full SHA
    ea83ebc View commit details
    Browse the repository at this point in the history

Commits on Sep 22, 2026

  1. Name the plugin microsoft-sql, after the repository

    The plugin takes the repository name, so it installs as microsoft-sql@microsoft-sql.
    Codex requires this anyway: it refuses a marketplace entry whose plugin.json name
    differs from the entry name, which is what stopped the scoped-collection experiment
    from installing there.
    croblesm committed Sep 22, 2026
    Configuration menu
    Copy the full SHA
    00cb8d8 View commit details
    Browse the repository at this point in the history
  2. Ship three scoped plugins beside the full collection

    One plugin carrying all 57 skills is wrong for three audiences at once. The
    MSSQL extension for Visual Studio Code already carries Data API builder
    tooling, so our two Data API builder skills clash there. A SQL Server
    Management Studio user is a database administrator and does not want ORMs or
    serverless bindings. The Azure SQL Database container is its own product.
    
    So catalog/plugins.json now says which skills each surface carries, and
    scripts/generate.mjs writes plugins/<name>/ from it: four manifests, a logo, a
    README saying the folder is generated, and byte copies of the skills.
    
      microsoft-sql                     57, unchanged, the whole collection
      microsoft-sql-vscode              23, no Data API builder
      microsoft-sql-ssms                15, diagnostics and operations
      microsoft-azuresql-db-container   18, the container and its feedback path
    
    Copies rather than symlinks or a manifest skill list, both measured and both
    lost. With every entry at source "./" and its own skills array, only Claude
    Code honoured the list: GitHub Copilot CLI printed a filtered count then
    loaded all 57, Cursor ignored it, and Codex refused the install because a
    marketplace entry name must match the name in that plugin's own plugin.json.
    With symlinks, Codex installed an empty skills directory and reported no
    error, and a Windows clone writes each link as a small text file. With copies,
    all four clients load exactly the subset.
    
    The parity gate now covers the copies file by file, sweeps a folder whose
    plugin left the data file, and refuses a list naming a skill with no content,
    a skill twice, or a skill its own mustNotInclude forbids. Each of those was
    planted and watched to fail. It also reports, without failing, how many skills
    in a plugin name a skill that plugin does not carry, which is how the Data API
    builder clash was found in the first place.
    
    Also fixes three README install lines that read microsoft@microsoft-sql. The
    plugin is named microsoft-sql, so none of them worked, and nothing gates that
    region of the file.
    croblesm committed Sep 22, 2026
    Configuration menu
    Copy the full SHA
    308baca View commit details
    Browse the repository at this point in the history
Loading