원클릭으로
report
// Trigger when the user wants a formatted HTML report file — DORA metrics report, PR cycle time report, engineering excellence report, coverage report, or retest analysis report. Not for quick questions (use devlake skill instead).
// Trigger when the user wants a formatted HTML report file — DORA metrics report, PR cycle time report, engineering excellence report, coverage report, or retest analysis report. Not for quick questions (use devlake skill instead).
This skill should be used whenever the user asks about engineering metrics, software delivery performance, or team productivity data — including PR statistics, DORA metrics (deployment frequency, lead time, change failure rate, recovery time), code coverage, CI/CD health, build success rates, flaky or failing tests, retest patterns, PR cycle time (coding time, pickup time, review time), merge throughput, incidents, or Jira feature tracking. Use this skill even when the user doesn't mention "DevLake" explicitly — any question about "how many PRs", "what's our deploy rate", "which tests are flaky", "compare team metrics", "coverage trends", "build failures", or "change failure rate" should trigger this skill. Also trigger for cross-team comparisons, historical trend analysis, bottleneck identification, and any request to query or analyze engineering data from repositories.
Trigger when the user wants to create a new GitLab repo for automated, scheduled engineering reports — setting up CI pipelines, DSPy prompts, and GitLab Pages publishing from DevLake data.
| name | report |
| description | Trigger when the user wants a formatted HTML report file — DORA metrics report, PR cycle time report, engineering excellence report, coverage report, or retest analysis report. Not for quick questions (use devlake skill instead). |
| disable-model-invocation | true |
Generate a structured HTML engineering report using DevLake MCP data. This skill follows the Generator pattern: load the DSPy task template, read the style guide, gather data, produce the report.
Read these as needed during report generation:
references/report-checklist.md — Quality checklist to verify the report before saving. Read this after generating the report to self-check.../../docs/.prompts/ — Existing prompt templates for coverage and retest reportsreferences/report-template.html — HTML/CSS design system with component usage guide| Category | MCP Tools to Use | Prompt Reference |
|---|---|---|
| DORA Metrics | get_deployment_frequency, get_lead_time_for_changes, get_failed_deployment_recovery_time | DORA 2025 benchmarks |
| PR Cycle Time | get_pr_cycle_time | Coding/Pickup/Review breakdown |
| Engineering Excellence | get_github_actions_health, analyze_pr_retests, get_pr_stats | Bottleneck score |
| Code Coverage | get_codecov_coverage, get_codecov_summary | docs/.prompts/coverage/ |
| Retest Analysis | analyze_pr_retests | docs/.prompts/quality_reports/ |
references/report-template.html — understand the CSS component library and placeholder formatproject_name — the DevLake project/organization nameget_deployment_frequency, get_lead_time_for_changes, get_failed_deployment_recovery_timeget_pr_cycle_time, get_pr_statsanalyze_pr_retestsget_codecov_coverage, get_codecov_summaryexecute_query with patterns from skills/devlake/references/sql-patterns.md{{REPORT_TITLE}}, {{BADGE_LABEL}}, {{REPORT_DATE}}, {{ANALYSIS_DAYS}}, etc.id and clickable .section-anchor.metrics-grid cards at the top, .executive-summary box, data tables with .explanation-box, and recommendationsreferences/report-checklist.md and verify the report against it<category>_report_<date>.htmlexecutive-summary not executiveSummary. The anchor links depend on this format..success (green) for good values, .warning (amber) for concerning, .danger (red) for critical, .info (cyan) for neutral. Don't hardcode color values.<canvas> charts if the data genuinely benefits from visualization. Tables are usually clearer for small datasets.