القائمة
Hardens code for production: edge cases, resilience, security, and polish. Use when preparing code for release, checking production-readiness, or hardening a feature.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Drives implementation outside-in: starts from an acceptance test for user-visible behavior, then works inward layer by layer, stubbing what doesn't exist yet. Use when building a feature across collaborating components to let design emerge from usage rather than speculation.
Autonomous end-to-end feature development with phased validation gates. Use when building major new functionality or adding substantial features.
End-to-end GitHub issue lifecycle: pick up an issue, create a worktree, build the fix or feature, open a PR, watch CI, and iterate until green. Use when picking up, fixing, or implementing a GitHub issue or ticket.
Decomposes work into ordered, shippable slices. Use when breaking down features, planning implementation order, or slicing work into deliverable increments.
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
Refactoring process. Invoke immediately when user or document mentions refactoring, or proactively when code gets too complex or messy.
| name | harden |
| description | Hardens code for production: edge cases, resilience, security, and polish. Use when preparing code for release, checking production-readiness, or hardening a feature. |
STARTER_CHARACTER = 🛡️
Production-readiness pass. Complete all four steps.
Walk through every category, add tests for gaps found:
See references/production-checklist.md for full checklist.
Address every item (mark N/A with reason if not applicable):
Invoke /refactoring on all files touched. This is a required step, not optional.
Two parts: coverage check, then style review.
Coverage — check that these exist where they should. Missing text is worse than imperfect text:
Style — invoke /writing-style on all text added or modified. This includes error messages, log messages, API docs, CLI output — not just UI copy.
All five checks must pass:
