mcpField
Q
qe-release

qe-release

github.com/proffesor-for-testingDevelopment51981 installsUpdated today
Repository

About qe-release

qe-release is a skill for managing an end-to-end npm release with verification gates and protection against hardcoded versions. It is intended for maintainers of a dual-package project and guides version checks, synchronized updates, and changelog edits.

Key features

  1. 01Audit version strings across the codebase
  2. 02Keep both package versions in sync
  3. 03Update the changelog in Keep a Changelog format
  4. 04Use verification gates in the release workflow

Use cases

  1. 01Prepare a dual-package npm release
  2. 02Find stale or hardcoded version strings
  3. 03Bump synchronized package versions
  4. 04Add a dated release section to the changelog

MCP support

This skill requires the AQE MCP server configured in `.kiro/settings/mcp.json`. It uses the `@agentic-qe` MCP server tools for QE fleet initialization, test generation, coverage analysis, quality assessment, and memory operations.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill qe-release

After installing, type/qe-releasein Claude Code to confirm it loaded.

Details

From the project README

qe-release

End-to-end npm release workflow with verification gates and hardcoded-version protection

Tags: qe, quality-engineering, release-management

Prerequisites

This skill requires the AQE MCP server. Ensure it is configured in .kiro/settings/mcp.json.

Steps

1. Architecture

This project has a dual-package structure — both must stay in sync:

2. Arguments
  • <version> — Target version (e.g., 3.5.5). If omitted, prompt the user.
3. Steps

Steps

4. Pre Flight Ensure Clean State
  1. Pre-Flight: Ensure Clean State
5. Version Audit

Read the current version from package.json (source of truth). Then grep the ENTIRE codebase for hardcoded version strings — current version, old versions, and any version-like patterns. Check both package.json files are in sync.

6. Bump Version

Update both package.json files to the target version:

7. Update Changelog

Add a new section to v3/CHANGELOG.md following Keep a Changelog format:

8. Version Yyyy Mm Dd

[] - YYYY-MM-DD

MCP Tools

Use AQE tools via the @agentic-qe MCP server:

  • @agentic-qe/fleet_init — Initialize the QE fleet
  • @agentic-qe/test_generate_enhanced — Generate tests
  • @agentic-qe/coverage_analyze_sublinear — Analyze coverage
  • @agentic-qe/quality_assess — Assess quality gates
  • @agentic-qe/memory_store — Store learned patterns
  • @agentic-qe/memory_query — Query past patterns

Comments

Markdown supported