菜单
Use this skill when a change may affect integration between frontend and backend, environment variables, Docker setup, API routes, request payloads, response shapes, or branch-safe feature delivery in an existing full-stack repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Specialized expertise in CI/CD pipelines, GitHub Actions, security audits (SCA, secrets), and automated quality checks. Use when modifying or troubleshooting .github/workflows, adding new CI checks, or ensuring repository integrity through automation.
Use this skill when the task is to create, rewrite, improve, structure, or update project documentation such as README files, setup guides, runbooks, operating procedures, installation steps, contributor guides, technical documentation, architecture notes, deployment guides, onboarding docs, and troubleshooting documentation in Markdown.
Use this skill when the task is to act as a senior full-stack developer and cybersecurity engineer for an existing web application repository, including repository analysis, secure architecture review, authorized web application pentest planning and execution, dependency and package review, version drift analysis, technology watch, upgrade recommendations, and safe remediation planning for Next.js, Tailwind CSS, Python backends, Docker, APIs, and CI/CD.
Use this skill for building or finishing frontend pages in an existing product repository, especially dashboard pages, settings screens, admin sections, detail views, empty states, forms, and responsive layouts in Next.js with Tailwind CSS.
Use this skill whenever the task involves editing an existing codebase and the goal is to minimize token usage, reduce code churn, avoid unnecessary refactors, keep patches reviewable, and change only what is strictly required.
Use this skill for Next.js App Router development in TypeScript or JavaScript, including app directory architecture, layouts, pages, route handlers, server components, client components, loading states, error boundaries, metadata, environment variables, and safe frontend changes in existing repositories.
| name | safe-integration-checker |
| description | Use this skill when a change may affect integration between frontend and backend, environment variables, Docker setup, API routes, request payloads, response shapes, or branch-safe feature delivery in an existing full-stack repository. |
Use this skill before or during changes that may break integration.
Catch integration risks early while keeping changes small.
For any integration-sensitive task, provide a compact check list:
Use short, operational language. Do not produce long explanations unless risk is high.
