From wathba-skills
If the repo has no CI the agent adds one. If it does the agent keeps it honest — lint, typecheck, tests, and migration hygiene as rules the agent can actually enforce.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wathba-skills:ci-hygieneThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill whenever the work touches the build pipeline, test runners, dependency installation, deploy workflows, or any change that can pass locally but break CI for the team.
Use this skill whenever the work touches the build pipeline, test runners, dependency installation, deploy workflows, or any change that can pass locally but break CI for the team.
Also use it when the work adds generated files, migration scripts, codegen, external service fixtures, package manager changes, GitHub Actions/GitLab CI/YAML workflows, Dockerfiles, or release automation.
Add a minimal pipeline that runs on every pull request:
Do not skip a step because "the repo doesn't have one yet" — add it in the same change.
latest tags, no unpinned actions, no mystery caches.secrets-baseline when CI variables, deploy tokens, package registry tokens, or cloud credentials are involved.testability-check when CI cannot run meaningful tests without invasive bootstrapping.scripts/ci-smoke.mjs locally before pushing a change that modifies the pipeline or the build configuration.Version: 0.6.0 · Last verified: 2026-04-24 · Status: maintainer-reviewed
Sources
npx claudepluginhub juribadev/wathba_auditor --plugin wathba-skillsProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.