Skip to content
Skills Library
DevOps & cloud · Review & audit

check-devops

/check-devops

Audits the current project against a 312-item backend, database, security, DevOps and distributed-systems checklist and writes an evidence-backed status report. Use when the user says "check-devops", types /check-devops, or asks for a production-readiness / DevOps / backend audit of the project.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Audits the current project against a 312-item backend, database, security, DevOps and distributed-systems checklist and writes an evidence-backed status report. Use when the user says "check-devops", types /check-devops, or asks for a production-readiness / DevOps / backend audit of the project.

Triggers from the description

check-devops
Original author description

Audits the current project against a 312-item backend, database, security, DevOps and distributed-systems checklist and writes an evidence-backed status report. Use when the user says "check-devops", types /check-devops, or asks for a production-readiness / DevOps / backend audit of the project.

How it works

  1. Steps
  2. Report format (in the user's language)
Original SKILL.md headings · 32 lines, 308 words
SKILL.md preview
---
name: check-devops
description: Audits the current project against a 312-item backend, database, security, DevOps and distributed-systems checklist and writes an evidence-backed status report. Use when the user says "check-devops", types /check-devops, or asks for a production-readiness / DevOps / backend audit of the project.
---

# check-devops

Audit the current project against `checklist.md` (in this folder, 312 items). Report only: do not change code.

## Steps

1. **Project profile** (main context, keep it short): project root, language/framework, how it runs and deploys
   (repo CLAUDE.md, package.json/pyproject/go.mod/Cargo.toml, Dockerfile/compose, CI files, IaC).
   Server-side settings (reverse proxy, firewall, backups, uptime monitoring, fail2ban) may live outside the repo:
   if a machine-level note exists (e.g. `~/CLAUDE.md`), read it and count those items as "covered by infrastructure".
2. **Parallel scan**: launch 8 Explore agents with `model: "sonnet"` in a single message, ~39 items each:
   1–39, 40–78, 79–117, 118–156, 157–195, 196–234, 235–273, 274–312.
   Put in each agent's prompt:
   - the project root + the profile from step 1,
   - the text of its item range (from `checklist.md`),
   - "If the repo has graphify-out/graph.json, use `graphify query \"<question>\"` first and read raw files only at the lines the graph points to.",
   - return one line per item: `No | Status | Evidence (file:line or command output summary) | Short note`.
     Status: ✅ present/correct · ⚠️ partial/weak · ❌ missing but needed · ➖ not applicable (reason in 3–5 words).
   - Never give ✅ without evidence; if it cannot find something, write "⚠️ unverified", not ❌. Conceptual items
     (e.g. Reading Documentation, Command Line Basics) get ➖ "conceptual".
3. **Merge** the results and write the report.

## Report format (in the user's language)

1. Summary: ✅/⚠️/❌/➖ counts and a one-sentence overall verdict.
2. **Priority gaps**: only ❌ and important ⚠️ items, ordered by impact (security and data loss first),
   each with: item, why it matters, the smallest suggested fix, evidence.
3. Full table to `<project>/docs/check-devops.md` (dated heading; overwrite a previous one and summarize
   the diff against the previous result). Do not print the full table in the terminal; give the file path.
4. Before fixing anything, ask the user which items to work on.
Files in this package (2)
  • SKILL.md 2 KB
  • checklist.md 7 KB

Versions

The database has no other skills named check-devops.

Database snapshot: 13.11.2026 · package version df2e0bf035e2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-audit
    Use when reviewing code or a codebase for DevOps readiness, security issues, and missing best practices
  • 96db-migrate
    [DevOps] Use when running or creating database migrations.
  • 96db-migrate
    [DevOps] Use when running or creating database migrations.
  • 100code-audit
    Use when reviewing or asked to review code quality, a codebase or pasted code for DevOps readiness, security issues and missing best practices (secrets, containers, Kubernetes, CI/CD, IaC, observability)
  • 100devops
    Use when unsure whether a request is a GitHub or Azure DevOps operation, or when someone says "devops help", "connect to devops", "check my work items or PRs", "devops?". Routes to devops-github or devops-azure based on intent. Also use as a fallback when a request doesn't clearly map to either one.
  • 100dx-devops-project-manage
    Use to list, view, or manage DevOps Center projects in a Salesforce org — show all projects, create a project, or update an existing project's name, description, or active status. Invoke to run sf devops project list on any listing request, or to create a project, set up a new…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.