Use it to run pre-release checks, verify a clean production build, package an extension, inspect the package and choose a semantic version change.

It reduces the chance of shipping software with failing tests, code-quality problems, build errors or incorrect package contents. Release management means coordinating these checks before publishing a new version.

How newbpydev/mcp-diagnostics-extension configures GitHub Copilot

Q: What is mcp-diagnostics-extension release-workflow.instructions.md?

A release-management checklist for preparing and shipping software. It covers tests, code checks, compilation, builds, packaging, version changes and release documentation.

Reuse

Borrowing it

Nothing to install: this file belongs to newbpydev/mcp-diagnostics-extension. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/newbpydev/mcp-diagnostics-extension/master/.github/instructions/release-workflow.instructions.md

Clone the repo

git clone --depth 1 https://github.com/newbpydev/mcp-diagnostics-extension

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/newbpydev/mcp-diagnostics-extension/release-workflow/github.svg)](https://agentmods.dev/instructions/newbpydev/mcp-diagnostics-extension/release-workflow)

Your own site

<a href="https://agentmods.dev/instructions/newbpydev/mcp-diagnostics-extension/release-workflow"><img src="https://agentmods.dev/badge/instructions/newbpydev/mcp-diagnostics-extension/release-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/newbpydev/mcp-diagnostics-extension/release-workflow"><img src="https://agentmods.dev/badge/instructions/newbpydev/mcp-diagnostics-extension/release-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,533 This file is loaded in full into every session.

When invoked 1,533 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.01533	$0.01533
Opus 5.5	$0.00613	$0.00613
Sonnet 5.5	$0.00307	$0.00307
Haiku 4.5	$0.00153	$0.00153

Measured 2mo ago against content hash f93fca31bb77, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-diagnostics-extension release-workflow.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/release-workflow.instructions.md · 240 lines

How it starts

The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Complete Release Management Workflow

This rule defines the comprehensive end-to-end release management workflow that must be followed for all software releases, based on industry best practices from LaunchDarkly and Zeet.

🎯 Overview

Every software release must follow this systematic checklist to minimize downtime risks, ensure quality, and maintain professional standards. This workflow combines traditional best practices with modern feature management approaches.

📋 Complete Release Management Checklist

Phase 1: Pre-Release Quality Assurance

1.1 Test Suite Validation

# Run comprehensive test suite
npm run test:ci

# Verify all tests pass (target: 100% pass rate)
# Check test coverage (target: >90%)
# Ensure no failing or skipped tests

1.2 Code Quality Checks

# Run linting
npm run lint

# Check code formatting
npm run format:check

# Verify TypeScript compilation
npm run compile

1.3 Build Verification

# Clean build
npm run clean
npm run compile:prod

# Package extension
npm run package

# Verify package contents and size

Phase 2: Version Management & Documentation

2.1 Semantic Versioning

# Choose appropriate version bump:
npm run release:patch    # Bug fixes (1.0.0 → 1.0.1)
npm run release:minor    # New features (1.0.0 → 1.1.0)
npm run release:major    # Breaking changes (1.0.0 → 2.0.0)

# For pre-releases:
npm run release:alpha    # Alpha releases
npm run release:beta     # Beta releases

2.2 Changelog Generation

Automatic: standard-version generates changelog from conventional commits
Manual Review: Verify changelog accuracy and completeness
Enhancement: Add detailed descriptions for major features/fixes

2.3 Documentation Updates

README.md: Update features, installation, usage instructions
API Documentation: Update MCP tools, resources, configuration
Troubleshooting: Add new known issues and solutions
Migration Guides: For breaking changes

Read the full file on GitHub · 240 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 240 lines · 1,533 tokens per session scan A f93fca31bb77

Subscribe to this mod's changes

mcp-diagnostics-extension release-workflow.instructions.md is an instructions file published in the GitHub repository newbpydev/mcp-diagnostics-extension (22 stars, last pushed 1y ago), licensed MIT. It adds 1,533 tokens to every session, about $0.0061 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases ai-agent-tools ai-tools clean-architecture diagnostic-tool diagnostics extension-development

mcp-diagnostics-extension release-workflow.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
mcp-diagnostics-extension release-workflow.instructions.mdnewbpydev/mcp-diagnostics-extension	Instructions file	22	1y ago	MIT	A	1,533	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

mcp-diagnostics-extension: Instructions file for GitHub Copilot