菜单
Safe deprecation of features and migration between versions. Use when removing features, changing APIs, or migrating data schemas. Covers deprecation notices, migration guides, and sunset timelines.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Security posture for the AI agent itself covering OWASP LLM Top 10, Agentic Security Top 10, behavior boundaries, destructive operation gates, prompt injection resistance, and skill supply chain verification via OIDC Trusted Publishing.
Design and implement clean, consistent, well-documented APIs and interfaces. Use when building REST APIs, GraphQL schemas, library interfaces, or internal module boundaries.
Ensure compliance with organizational policies and regulatory standards, then generate structured reports and dashboards. Covers license auditing, data handling regulations, security standard mapping, and structured reporting with actionable recommendations.
Collaborative design refinement with hard gates preventing premature implementation. Use BEFORE any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Visual verification of UI changes using browser DevTools MCP. Use when building or modifying frontend components to verify rendering, responsiveness, and visual correctness. All browser-read data is treated as UNTRUSTED.
End-to-end pipeline from CI configuration through production deployment. Covers pipeline stages, test automation, deployment strategies, pre-launch checklists, rollback planning, and post-deploy verification.
| name | deprecation-and-migration |
| description | Safe deprecation of features and migration between versions. Use when removing features, changing APIs, or migrating data schemas. Covers deprecation notices, migration guides, and sunset timelines. |
| version | 1.0.0 |
| permissions | ["fs.read","fs.write","shell.exec"] |
| triggers | [{"context":"deprecating a feature"},{"context":"removing an API endpoint"},{"context":"migrating data schemas"},{"command":"/ship"}] |
| platforms | ["claude-code","cursor","gemini-cli","copilot","codex","opencode","windsurf","kiro"] |
| dependencies | ["git-workflow-and-versioning@^1.0.0"] |
| author | codehands-core |
| signed | true |
| tier | 2 |
Deprecation is making a promise: "this will be removed, here's what to use instead, and here's how much time you have." This skill ensures deprecated features have clear notices, migration paths, and respectful timelines.
Before removing anything, add a deprecation notice:
/**
* @deprecated Use `newFunction()` instead. Will be removed in v3.0.0.
*/
function oldFunction() { ... }
Write a migration guide:
## Migrating from v1 to v2
### Breaking Changes
1. `oldFunction()` removed → use `newFunction()`
2. `/api/v1/users` removed → use `/api/v2/users`
### Step-by-Step
1. Update import: `import { newFunction } from 'package'`
2. Replace all calls to `oldFunction(a, b)` with `newFunction({ a, b })`
3. Run tests to verify
| Rationalization | Reality |
|---|---|
| "Nobody uses this feature" | If you don't have usage metrics, you don't know. Add deprecation logging first, then decide. |
| "We can just remove it" | Removing without notice breaks consumers. Even internal consumers. Deprecate first. |
codehands:git-workflow-and-versioning — Semver for breaking changescodehands:documentation-and-adrs — ADR for deprecation decision