القائمة
End-to-end npm release workflow with verification gates and hardcoded-version protection
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill qe-releaseيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.
Build dependency-aware execution plans for complex Agentic QE, Ruflo, integration, migration, or multi-stream engineering programs. Use when Codex must turn research or requirements into phased work, select a small AQE fleet, map critical paths and parallel streams, define acceptance gates, or sequence risky changes. Use aqe-plan-quality instead when the primary output is only a test or quality plan.
Conduct evidence-first technical research for Agentic QE, Ruflo, related ruvnet projects, or external tools. Use when Codex must investigate a repository, compare current upstream changes, trace dependencies and history, distinguish verified facts from inference, or synthesize findings into actionable engineering recommendations. Do not use for a simple known-answer lookup or an implementation-only task.
| inclusion | auto |
| name | qe-release |
| description | End-to-end npm release workflow with verification gates and hardcoded-version protection |
End-to-end npm release workflow with verification gates and hardcoded-version protection
Tags: qe, quality-engineering, release-management
This skill requires the AQE MCP server. Ensure it is configured in .kiro/settings/mcp.json.
This project has a dual-package structure — both must stay in sync:
<version> — Target version (e.g., 3.5.5). If omitted, prompt the user.Steps
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.
Update both package.json files to the target version:
Add a new section to v3/CHANGELOG.md following Keep a Changelog format:
[] - YYYY-MM-DD
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