gitops-pipeline-developer

Author production-ready GitOps release pipelines (Jenkins-style by default; portable patterns for GitHub Actions, GitLab CI, Drone) that combine Gitflow branching, Conventional Commits, automatic SemVer bumping, a SonarQube quality gate, Grype container image scanning, and an aggregated quality+security scorecard with policy alignment checks. Use this skill whenever the user wants to write or harden a CI/CD pipeline, set up a release flow, automate versioning, enforce conventional commits, gate merges on SonarQube, scan images with Grype, build a release scorecard, or hits you with phrases like "set up the CI", "write me a Jenkinsfile", "add SonarQube", "enforce conventional commits", "wire SemVer", "scan our images for CVEs", "add a quality gate", "CI for this repo", or "I need a release pipeline".

Aller à l'installation

Dépôt: MKAbuMattar/skills
Dernière activité de la source: 26 juillet 2026 à 14:07
Langue détectée de SKILL.md: anglais
Étoiles: 1
Forks: 1

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/MKAbuMattar/skills --skill gitops-pipeline-developer

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

47 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

humanizer

Edit or review text to remove signs of AI-generated writing — inflated significance ('pivotal moment', 'evolving landscape'), promotional language ('nestled', 'breathtaking'), superficial -ing analyses ('highlighting', 'underscoring'), vague attributions ('industry experts'), em-dash overuse, rule-of-three patterns, AI vocabulary ('delve', 'tapestry'), copula avoidance ('serves as'), passive voice, negative parallelisms ('not just X, but Y'), filler phrases, sycophantic openings ('Great question!'), and the rest of the 29-pattern catalog from Wikipedia's 'Signs of AI writing'. Works on written prose only: essays, articles, drafts, documentation, emails, marketing copy. Use this skill whenever the user wants to humanize text, remove AI tells, edit AI-sounding writing, make text sound less like ChatGPT, do a final 'does this read like a person wrote it' pass, or hits you with phrases like 'humanize this', 'make this sound less AI', 'remove the AI slop', 'edit this draft', or 'why does this read like an LLM'.

2026-07-28

linux-script-developer

Write production-ready Bash scripts with strict error handling (`set -euo pipefail`), validated argument parsing, colored user feedback, and cross-platform compatibility (Linux, macOS, Windows via Git Bash/WSL). Use this skill whenever the user asks for a `.sh` script, a shell script, a Bash one-liner installer, a CLI wrapper, or a file-batch processor, and for server and deployment automation generally: releasing or rolling back a build, restarting or health-checking a service, scheduled and cron jobs, log rotation, backup and restore, syncing files between machines, and bootstrapping a box. Includes casual phrasings like "write a script to ...", "automate this in bash", or "make me a shell tool". Also use when reviewing or hardening an existing Bash script.

2026-07-28

teacher-mode

Explain any concept like an experienced mentor: clear, first-principles, and brief. Use this skill whenever the user wants to understand something rather than just get it fixed, including "explain", "teach me", "how does X work", "why does X", "what is X", "help me understand", "walk me through", "ELI5", "deep dive", or "I'm learning X". Conceptual questions get answered in full; on a concrete coding task it withholds the working solution and leads with hints until the learner attempts it. Do not use when the user wants the job done rather than explained.

2026-07-27

Tout voir dans ce dépôt

GitOps Pipeline Developer

Author production GitOps release pipelines that combine Gitflow + SemVer + Conventional Commits with a SonarQube + Grype quality gate and a single Score & Alignments scorecard.

When to use

The user wants to write a new CI/CD pipeline (Jenkinsfile / .github/workflows / .gitlab-ci.yml).

The user wants to harden an existing pipeline with SonarQube, Grype, conventional commits, or SemVer.

The user wants a "release scorecard" — a single number (0–100) plus policy alignment checks gating each merge or release.

A task chain ends in "and put it behind the CI quality gate".

The release model in one paragraph

Gitflow — long-lived main (production) + develop (integration), short-lived feature/*, release/*, hotfix/*. Releases merge to main and develop; hotfixes branch from main. Conventional Commits — every commit is <type>(scope): subject (feat:, fix:, chore:, docs:, test:, refactor:, perf:, build:, ci:, BREAKING CHANGE: footer). Enforced by commitlint in CI and locally via a Husky commit-msg hook. SemVer — bumps are derived from commits since the last tag: feat: → minor, fix:/perf: → patch, BREAKING CHANGE: → major. semantic-release (or an equivalent) reads the commit history, decides the next version, writes the tag, and updates CHANGELOG.md. Prerelease branches (develop, release/*) get suffixed tags (1.4.0-rc.1, 1.4.0-beta.3).

The pipeline enforces all three: a commit that doesn't match Conventional Commits fails CI before tests run; the SemVer bump is computed automatically with no human input; merges to main only succeed when both the SonarQube quality gate and Grype severity gate pass.