القائمة
Use this skill for public release readiness checks where package contents, metadata, documentation, dry runs, and publication gates must be verified before publishing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill for backend API, DTO, or enum changes that require frontend request wrappers, types, enums, or UI adaptations.
Use this skill for durable execution records, runbooks, evidence folders, artifacts, and validation of archive layout after task completion.
Use this skill for validated local commit and optional push workflows where scope, staged content, identity, gates, and human confirmation must be handled explicitly.
Use this skill for desktop productivity UI design systems, design tokens, dense tables, status markers, theme tokens, and non-AI-looking Electron app visual standards.
Use this skill for Electron desktop packaging and release readiness across Windows, macOS, and Linux, including signing boundaries, artifacts, dry-runs, and public release checks.
Use this skill for cross-platform desktop UI QA of Electron apps, including renderer screenshots, native window behavior, shell prerequisites, task logs, and platform-specific checks.
| name | release-guard |
| description | Use this skill for public release readiness checks where package contents, metadata, documentation, dry runs, and publication gates must be verified before publishing. |
| os | cross-platform |
Use this Skill when the situation matches the frontmatter description. It is cross-platform and tool-neutral: judgment, sequencing, risk boundaries, and human confirmation points live here; deterministic checks should be delegated to installed workflow runtime paths first, then to source repository paths when the runtime is not installed.
os: cross-platform. Use the repository's declared package manager and language tooling. Treat missing release tooling as a readiness gap, not permission to install dependencies.
Prefer installed runtime paths:
~/.agent-routines/workflows.agent-routines/workflowsSource fallback:
workflows/<workflow-name>/Recommended workflows: release-check, security-check, node-workspace-check, gate-check
Ask before publishing, tagging, pushing, mutating versions, changing registry configuration, creating GitHub releases, or running dependency installation.
Separate source validation, package-content leaks, metadata gaps, dry-run failures, and external authorization blockers. Do not claim release readiness from local checks alone when external proof is missing.