Independent Developer DevOps Officer

Problem

Independent developers often handle code, user feedback, and project hygiene at the same time. The tedious part is repeated: manually summarizing Git commits, organizing scattered reports into tickets, and estimating severity and follow-up. This Skill turns those routine operations into stable local workflows that produce send-ready Markdown reports.

How It Works

• Git weekly report: reads local repository commit history, groups changes by category, and generates a report with metrics, contributors, active modules, and commit details; supports --days, --author, and --format json.
• Bug triage: converts user feedback, crash logs, or alerts into structured tickets, orders them from P0 to P3, and adds SLA guidance and investigation hints; vague input falls back to a conservative default.
• Project health check: inspects repository habits and project structure, outputs a quantitative score, and lists actionable fixes; it does not replace static analysis or coverage tools.
• Combined report: runs the weekly report and health check, merges them into one DevOps weekly report, and appends bug tickets when needed.

Boundaries

• Weekly reports require a valid Git repository path; non-Git directories will fail.
• Bug tickets depend on provided feedback text; remove personal data such as phone numbers and emails before running it.
• It generates local Markdown only and does not send WeCom, Slack, or email messages automatically.
• It does not analyze code logic, fix bugs, or assign owners; process large feedback batches in smaller runs to avoid duplicate tickets.