القائمة
CI/CD discipline — pipeline structure, credentials, debugging methodology, gates. Tool-agnostic; the CI platform comes from memory-long §stack.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Context engineering — memory navigation, textual graph traversal, progressive disclosure, recovery. Load when assembling context for a task or when lost.
Implementation-side security discipline — headers, dependencies, secrets, authz. Load for hardening work (sec-ops domain).
Commit conventions, branching, anchors in messages, and the git safety rules. Load for any git operation beyond status/diff.
Anti-generic-AI design discipline — bans, tells, and the slop test. Load for ANY new UI surface or visual redesign. Inspired by Impeccable (Apache 2.0).
Motion & animation discipline — purpose, performance, reduced-motion. Load when work involves animation, transitions or scroll effects.
Microcopy discipline — buttons, errors, empty/loading/success states, alt text. Voice and tone come from the project's memory, not from this skill.
| name | pipeline-discipline |
| description | CI/CD discipline — pipeline structure, credentials, debugging methodology, gates. Tool-agnostic; the CI platform comes from memory-long §stack. |
Tool-agnostic (GitHub Actions, GitLab CI, Jenkins — from memory-long §stack). Complements ops-dev instructions (always-on rules); this is the deep-dive.
validate (lint/format/types, fast-fail) → build/plan (artifacts or IaC plan) → gate (tests, security scan, human approval where required) → apply/deploy → verify (smoke, health). Each stage fails the pipeline honestly — no continue-on-error on gates.
contents: read unless proven otherwise).Pipeline auth failures are almost always one of, in this order: ① missing job permissions declaration · ② wrong role/identity ARN or audience · ③ trust condition not matching the repo/branch pattern (verify the exact sub claim format) · ④ backend/state store unreachable or under-permissioned. Check the boring things first — read the error, not the vibes.
Cache dependency stores keyed on lockfile hash · timeout every job (a hung job is a silent cost) · artifacts have retention policies · matrix builds only where variants genuinely differ · re-run flaky jobs is a diagnosis, not a fix — flakiness gets an issue.
Never weaken a gate to go green · pin action/image versions · deploy triggers propose, human executes · every pipeline change states its verification (dry-run or which gate proves it).