Menu
How to harden pre-commit against release-only failures, especially packaging mismatches
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
{what this skill teaches agents}
Excel CLI automation skill for Windows workbooks. Use when a coding agent needs token-efficient, scriptable, or unattended Excel automation via excelcli commands. Best for CI/CD, scheduled jobs, batch processing, PowerShell workflows, and bulk workbook edits. Supports Power Query, DAX, PivotTables, Tables, Ranges, Charts, VBA, Data Models, screenshots, and formatting. Triggers: excelcli, Excel CLI, command line, batch, script, automation, CI/CD, scheduled, PowerShell, unattended, coding agent, workbook processing.
Excel MCP Server skill for Windows workbook automation. Use when an assistant needs rich MCP tools to create, inspect, modify, format, or analyze Excel files. Supports Power Query (M), Data Model/DAX, PivotTables, Tables, Ranges, Charts, Slicers, formatting, screenshots, VBA macros, connections, and calculation mode. Triggers: Excel, spreadsheet, workbook, xlsx, xlsm, Power Query, DAX, PivotTable, chart, dashboard, VBA, MCP.
{what this skill teaches agents}
Catch packaging-script regressions by asserting the real script exit path and current overlay surface.
Use a validated tooling downgrade when Dependabot flags an unpatchable transitive vulnerability in build-only dependencies.
| name | precommit-release-gates |
| description | How to harden pre-commit against release-only failures, especially packaging mismatches |
| domain | release-management |
| confidence | high |
| source | earned |
Use this when a release workflow fails even though local builds or lighter smoke checks were green.
npm run package, not just npm install or npm run compile).scripts/pre-commit.ps1 if the failure is deterministic and commit-blocking.package.json and package-lock.json).vscode-extension/package.json and vscode-extension/package-lock.json both moved engines.vscode to ^1.110.0 to match @types/vscode ^1.110.0.scripts/pre-commit.ps1 now runs the same npm run package path that release uses.