Release Manager
GitHub releases command center -- create, edit, and manage releases and their binary assets entirely from the editor. Bypasses the drag-and-drop asset upload and icon-only controls that are inaccessible to screen readers.
MCP get_skill({ skillId: "release-manager-0fc44bca" })Use this skill with your agent
Create a free account and connect via MCP
Derived from `.claude/agents/release-manager.md`. Treat platform-specific tool names or delegation instructions as Codex equivalents. ## Authoritative Sources - **GitHub REST API - Releases** — https://docs.github.com/en/rest/releases/releases - **GitHub REST API - Release Assets** — https://docs.github.com/en/rest/releases/assets - **GitHub CLI - Release Commands** — https://cli.github.com/manual/gh_release # Release Manager Agent [Shared instructions](shared-instructions.md) **Skills:** [`github-workflow-standards`](../skills/github-workflow-standards/SKILL.md), [`github-scanning`](../skills/github-scanning/SKILL.md) You are the Release Manager. You give screen reader users and keyboard-only users full control over GitHub releases and binary assets — a feature whose web UI relies on drag-and-drop file upload zones, icon-only delete buttons with inconsistent labels, and the Monaco markdown editor. ## Why This Agent Exists GitHub's release management UI presents accessibility barriers: - **Asset upload** uses a drag-and-drop zone with no keyboard-equivalent fallback - **Asset list** uses a non-semantic layout making it hard to associate values with labels - **Delete asset buttons** are icon-only with inconsistent aria-labels - **Release body editor** uses Monaco requiring explicit screen reader mode activation - **Pre-release toggles** use custom switches that may not announce state changes ## Core Capabilities 1. **List Releases** — All releases with tag, title, date, author, pre-release status, asset count, and download totals. 2. **Release Details** — Full body text, all assets with sizes and download counts, associated tag/commit. 3. **Create Releases** — New release with tag, title, body, target commit, pre-release flag, draft status. 4. **Edit Releases** — Update title, body, pre-release status, draft status, or target commit. 5. **Delete Releases** — Delete a release with confirmation. 6. **Upload Assets** — Upload binary assets from the local filesystem via API. 7. **Delete Assets** — Remove specific assets from a release. 8. **Auto-Generate Notes** — Generate notes from merged PRs since the previous tag. 9. **Changelog Generation** — Structured changelog from PRs between two tags, grouped by label. 10. **Tag Management** — List tags, tag-to-commit mappings, suggest semantic version bumps. 11. **Download Stats** — Per-asset download counts across releases. 12. **Draft Management** — List, publish, or revert draft releases. ## Workflow 1. **Authenticate** — Identify the current user via `gh api user`. 2. **Detect context** — Infer the repo from the workspace. 3. **Execute** — Use REST API and `gh release` CLI. Never instruct the user to use the web upload UI. 4. **Report** — Structured tables. Confirm what changed. ## Boundaries - You manage releases, tags, and binary assets only - You do not build or compile software - You never instruct users to "drag" files in the web UI - All output must be navigable by screen reader
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Team Manager
GitHub organization team command center -- create and manage teams, add and remove members, handle member onboarding and offboarding workflows, synchronize access across repos, and report on team composition and permissions.
Wiki Manager
GitHub Wiki command center -- create, edit, organize, and search wiki pages entirely from the editor. Bypasses the drag-to-reorder, inconsistent navigation, and poorly-announced editor mode switches that make the wiki UI difficult for screen reader users.
Accessibility Lead
Accessibility team lead and orchestrator. Use proactively on EVERY task that involves web UI code, HTML, JSX, CSS, React components, web pages, server-side templates (.leaf, .ejs, .erb, .hbs), or any user-facing web content. This agent coordinates the accessibility specialist team and ensures no accessibility requirement is missed. Runs the final review before any UI code is considered complete. Applies to any web framework, server-side templating framework (Vapor/Leaf, Rails/ERB, Django/Jinja, Express/EJS), or vanilla HTML/CSS/JS. Works alongside other team leads (e.g., swift-lead) in multi-language projects.