leomajewski
- 3 skills
- 0 followers
- 6 hours ago last updated
- ▌ Cicd Pipeline · leomajewskiMethod and checklists for shipping a containerized application with GitHub Actions, Docker and Kubernetes — build once, publish a signed immutable image, promote that exact digest through gated environments to production. Covers the inventory to gather first, the dev/infra boundary, build-once/promote-by-digest, supply-chain integrity, deployment strategies, secrets, health-gated rollout, GitHub Environments approvals, and rollback. Use when asked to create or configure a pipeline, onboard an app to CI/CD, set up an environment, promote to production, or migrate a hand-run deploy to an automated one.
- ▌ Writing Style · leomajewskiWriting standard for technical documentation, replies and written communication — clarity, concision, objectivity and precision, cohesion, correctness, impersonality, completeness. Use when writing or reviewing any text (documentation, wiki page, README, procedure, summary, email, ticket, long reply).
- ▌ Network Troubleshooting · leomajewskiStructured method for troubleshooting infrastructure, networks and systems — initial scoping, zero assumptions, IS/IS NOT (Kepner-Tregoe), the scientific method, bottom-up OSI, 5 whys, an incident file, time-boxing and post-incident review. Use when investigating incidents, failures, outages, slowness, intermittent or unexpected behavior of a network/service/server, or whenever something is reported as "broken", "down" or "acting weird".