qe-release
End-to-end npm release workflow with verification gates and hardcoded-version protection
Best use case
qe-release is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
End-to-end npm release workflow with verification gates and hardcoded-version protection
Teams using qe-release should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/qe-release/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How qe-release Compares
| Feature / Agent | qe-release | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
End-to-end npm release workflow with verification gates and hardcoded-version protection
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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 [<version>] - 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
Related Skills
qe-github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
release
End-to-end npm release workflow with verification gates and hardcoded-version protection
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
qe-visual-testing-advanced
Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.
qe-verification-quality
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
qe-testability-scoring
AI-powered testability assessment using 10 principles of intrinsic testability with Playwright and optional Vibium integration. Evaluates web applications against Observability, Controllability, Algorithmic Simplicity, Transparency, Stability, Explainability, Unbugginess, Smallness, Decomposability, and Similarity. Use when assessing software testability, evaluating test readiness, identifying testability improvements, or generating testability reports.
qe-test-reporting-analytics
Advanced test reporting, quality dashboards, predictive analytics, trend analysis, and executive reporting for QE metrics. Use when communicating quality status, tracking trends, or making data-driven decisions.
qe-test-idea-rewriting
Transform passive 'Verify X' test descriptions into active, observable test actions. Use when test ideas lack specificity, use vague language, or fail quality validation. Converts to action-verb format for clearer, more testable descriptions.
qe-test-environment-management
Test environment provisioning, infrastructure as code for testing, Docker/Kubernetes for test environments, service virtualization, and cost optimization. Use when managing test infrastructure, ensuring environment parity, or optimizing testing costs.
qe-test-design-techniques
Systematic test design with boundary value analysis, equivalence partitioning, decision tables, state transition testing, and combinatorial testing. Use when designing comprehensive test cases, reducing redundant tests, or ensuring systematic coverage.
qe-test-data-management
Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios.
qe-test-automation-strategy
Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.