SKILL: docops
Purpose
Create formal reports (EN) and generate PDF/DOCX-ready content with consistent structure.
When to Use
- •When the task matches: Docs / Reports
Inputs
- •Task: (string) what to do
- •Context: (logs, stack traces, file paths, snippets)
- •Constraints: (must keep behavior, must pass lint/build, security limits)
Outputs
- •Fix plan + exact edits (file-by-file)
- •Commands to verify (PowerShell preferred)
- •Risk notes + rollback steps
Tooling
- •Primary: PowerShell, Node.js (npm), Git
- •Secondary: Python (optional)
Procedure (Gold Standard)
- •Reproduce / confirm error (command + expected output)
- •Identify root cause (single sentence + evidence)
- •Apply minimal patch (small diff)
- •Verify (lint/build/test)
- •Cleanup (remove unused imports, format, docs)
- •Provide PR-ready summary
Guardrails
- •Avoid broad refactors unless necessary
- •Never disable lint/test as “fix” without explicit approval
- •Keep changes localized; prefer small commits
Acceptance Criteria
- •npm run lint passes
- •npm run build passes
- •Feature still works (smoke test)