القائمة
Use when designing or improving a continuous integration pipeline for a software project
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/jeffreytse/grimoire-core --skill design-ci-pipelineيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when comparing very differently-titled roles for compensation banding, leveling, or organizational design — score each role's inherent Know-How (knowledge, skills, experience required), Problem Solving (complexity and freedom of thinking, scored as a percentage of Know-How), and Accountability (freedom to act and magnitude of impact), because job titles and informal seniority perceptions vary inconsistently across departments and don't provide a comparable basis on their own.
Use when many people request your scarce time, mentorship, or expertise and you cannot evaluate their genuine commitment level from a conversation alone — require a specific, costly, objectively verifiable unit of self-directed output (a set number of completed attempts) before engaging, because genuine commitment is what a conversation cannot reliably reveal but a completed, verifiable body of work can.
Use when deciding how to allocate a manager's or leader's limited time across competing activities — before defaulting to whatever is most urgent, estimate each candidate activity's leverage (how many people's output it affects, for how long, and whether it requires your specific position), because a manager's actual output is the output of the organization under their influence, not their own individual task completion.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | design-ci-pipeline |
| description | Use when designing or improving a continuous integration pipeline for a software project |
| source | "Accelerate" — Forsgren, Humble & Kim (IT Revolution, 2018); DORA metrics (dora.dev); Trunk-Based Development (trunkbaseddevelopment.com) |
| tags | ["ci","devops","dora","pipeline","automation","trunk-based-development"] |
| verified | true |
Design a CI pipeline that gives fast, reliable feedback on every commit and enables trunk-based development at scale.
Adopted by: Google, Netflix, Amazon, Etsy — all DORA elite performers with documented CI/CD practices Impact: DORA research (Accelerate, 2018) shows elite performers have 46× more frequent deployments and 2,555× faster lead time to change; fast CI (<10 min) is a key differentiator between elite and low performers.
Why best: A well-designed CI pipeline is the heartbeat of software delivery. It enforces quality gates, provides rapid feedback, and is the foundation that makes trunk-based development safe at scale. Slow or flaky CI is one of the highest-leverage engineering problems to fix.
GitHub Actions structure:
jobs:
lint: # 1 min
unit-test: # 3 min, parallel matrix [node18, node20]
build: # 2 min, depends on unit-test
security: # 2 min, parallel with build
integration: # 5 min, depends on build
Total wall time: ~8 minutes via parallelism.
npm install from scratch on every run adds 2-3 minutes; cache the node_modules layer.