ankyr-ci-release

Promotes staging release tags to main and prepares Cursor marketplace submissions after a release gate.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-ci-release-guyerreich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ankyr-ci-release
Source: https://github.com/GuyErreich/AI_Agents/tree/main/plugins/ankyr-git/skills/ankyr-ci-release
Command: npx skills add https://github.com/GuyErreich/AI_Agents --skill ankyr-ci-release-guyerreich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Promoting a version from staging to production involves multiple risky steps—running release gates, triggering promotion workflows, creating production tags, and submitting to the Cursor marketplace—where a mistake can publish an unvetted release. This Skill enforces a consent-first, gated workflow so nothing ships without explicit approval. ## Core Features & Use Cases - Release Gate Enforcement: Runs scripts/release_gate.py and records pass/fail from the exit code, halting the workflow on failure. - Staging-to-Production Promotion: Triggers the GitHub Actions promote.yml workflow with a dry run first, then a real promotion only with explicit consent. - Marketplace Publish Guidance: Reminds the user about GitHub Release creation via publish-production.yml, manual Cursor public marketplace review, and team marketplace Auto Refresh. - Use Case: After tagging 1.4.0-rc on staging, ask the agent to promote it to main; it runs the release gate, dry-runs the promotion workflow, and waits for your explicit go-ahead before executing. ## Quick Start Ask the agent to run the release gate and promote the current staging rc tag to main with a dry run first.

Frequently Asked Questions about ankyr-ci-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I promote a staging tag to production with GitHub Actions?▼

Run the release gate first, then dispatch the promote.yml workflow with gh workflow run using from_tag set to the rc tag and to_branch set to main. Always execute with dry_run=true first, then dry_run=false only after explicit consent.

How to publish a Cursor plugin to the marketplace?▼

Submit the repository at cursor.com/marketplace/publish after a production tag exists on main. Public marketplace updates are manually reviewed by Cursor, while team marketplaces load main directly and can use Auto Refresh with the Cursor GitHub App.

What happens if the release gate fails before promotion?▼

The workflow stops immediately when scripts/release_gate.py returns a failing exit code. The pass/fail result is recorded, and no promotion, tagging, or publishing steps continue until the gate passes.

Can the agent push tags or merge release PRs automatically?▼

No. The Skill explicitly forbids pushing tags, merging release PRs, promoting to main, or submitting to the public marketplace without explicit user consent for that specific action, including staging rc publishes.

Does this workflow require GitHub App secrets?▼

Yes, the preferred staging-to-production path uses the promote.yml Actions workflow, which requires GitHub App secrets configured in the repository. The production environment in publish-production.yml may also require a designated reviewer.