菜单
Repository maintenance for devantler-tech/reusable-workflows — triage, action/workflow version hygiene, backward-compatible workflow health, and consistency across the shared CI/CD building blocks. Use when performing autonomous or on-request maintenance of this repo.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
| name | maintain |
| description | Repository maintenance for devantler-tech/reusable-workflows — triage, action/workflow version hygiene, backward-compatible workflow health, and consistency across the shared CI/CD building blocks. Use when performing autonomous or on-request maintenance of this repo. |
Perform maintenance per the ## Maintenance section of this repo's AGENTS.md, within the shared devantler-tech maintenance conventions it references. High care: changes here ripple to every consumer repo — prefer additive, backward-compatible changes. A draft PR is the checkpoint; never merge external PRs or self-merge your own unreviewed drafts.
