Repository navigation
Comparing changes
Open a pull request
base repository: microsoft/microsoft-sql
base: main
head repository: microsoft/microsoft-sql
compare: rename-plugin-microsoft-sql
- 14 commits
- 215 files changed
- 1 contributor
Commits on Sep 18, 2026
-
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.
Configuration menu - View commit details
-
Copy full SHA for a8d1977 - Browse repository at this point
Copy the full SHA a8d1977View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for d6c6443 - Browse repository at this point
Copy the full SHA d6c6443View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for aab18c2 - Browse repository at this point
Copy the full SHA aab18c2View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for 1cfeb8f - Browse repository at this point
Copy the full SHA 1cfeb8fView commit details -
Configuration menu - View commit details
-
Copy full SHA for a37e159 - Browse repository at this point
Copy the full SHA a37e159View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1ee4187 - Browse repository at this point
Copy the full SHA 1ee4187View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for b0d4328 - Browse repository at this point
Copy the full SHA b0d4328View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for 0dd9e16 - Browse repository at this point
Copy the full SHA 0dd9e16View commit details -
Merge remote-tracking branch 'origin/main' into rename-plugin-microso…
…ft-sql # Conflicts: # llms.txt
Configuration menu - View commit details
-
Copy full SHA for 8dffca7 - Browse repository at this point
Copy the full SHA 8dffca7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 73e630e - Browse repository at this point
Copy the full SHA 73e630eView commit details -
Merge remote-tracking branch 'origin/main' into rename-plugin-microso…
…ft-sql # Conflicts: # llms.txt
Configuration menu - View commit details
-
Copy full SHA for 20ecdf6 - Browse repository at this point
Copy the full SHA 20ecdf6View commit details
Commits on Sep 19, 2026
-
Configuration menu - View commit details
-
Copy full SHA for ea83ebc - Browse repository at this point
Copy the full SHA ea83ebcView commit details
Commits on Sep 22, 2026
-
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.
Configuration menu - View commit details
-
Copy full SHA for 00cb8d8 - Browse repository at this point
Copy the full SHA 00cb8d8View commit details -
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.
Configuration menu - View commit details
-
Copy full SHA for 308baca - Browse repository at this point
Copy the full SHA 308bacaView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...rename-plugin-microsoft-sql