تشغيل أي مهارة في Manus بنقرة واحدة

dso-test-quality-report

النجوم٦

التفرعات١

آخر تحديث٢١ مايو ٢٠٢٦ في ٢٢:٥٢

Surfaces calibration program health by running the monthly and quarterly calibration reports. Use when checking test-quality calibration trends, reviewing reviewer calibration data, or auditing the calibration program status. Trigger phrases include '/dso:test-quality-report', 'run calibration report', 'show calibration health', 'test quality report'.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

navapbc

navapbc/digital-service-orchestra

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

SKILL.md

readonly

name	dso:test-quality-report
description	Surfaces calibration program health by running the monthly and quarterly calibration reports. Use when checking test-quality calibration trends, reviewing reviewer calibration data, or auditing the calibration program status. Trigger phrases include '/dso:test-quality-report', 'run calibration report', 'show calibration health', 'test quality report'.
user-invocable	true
allowed-tools	Bash, Read

Test Quality Report

Runs the calibration program health reports (monthly and quarterly) and surfaces their outputs.

Prerequisites

Calibration tracking tickets must exist. If they are absent, create them first:

bash .claude/scripts/dso-bootstrap-calibration-tickets.sh

Invocation

/dso:test-quality-report

Steps

Step 1: Run Monthly Report

.claude/scripts/dso calibration-report.sh monthly

Surface the full output to the user.

Step 2: Run Quarterly Report

.claude/scripts/dso calibration-report.sh quarterly

Surface the full output to the user.

Step 3: Summary

After both reports complete, provide a one-paragraph summary of the calibration program health, highlighting any trends, gaps, or action items surfaced by the reports.

المزيد من هذا المستودع

نفس المستودع

debug-everything

navapbc/digital-service-orchestra

Use when the user wants a comprehensive multi-issue health pass — fix all bugs, resolve broken tests, clear CI failures, fix lint and type errors, restore green builds — not for a single targeted bug fix. Diagnoses and resolves every outstanding open bug ticket plus all validation failures (test, lint, type, format, infrastructure) using orchestrated sub-agents with TDD discipline, in tier order. Trigger phrases include 'debug everything', 'fix all bugs', 'fix the failing tests', 'CI is failing', 'build is broken', 'clean up the codebase', 'restore green', 'project health pass'.

2026-06-076

end-session

navapbc/digital-service-orchestra

Use when wrapping up a worktree session — closing tasks, finishing work, or merging the branch back to main. Closes completed tickets, sweeps orphaned epics, extracts technical learnings, files bug tickets for unfixed failures, commits remaining changes, syncs the tickets branch, merges to main via merge-to-main.sh, verifies the worktree is merged and clean for claude-safe auto-removal, and prints a task summary. Trigger phrases include 'end session', 'wrap up', 'finish', 'done for now', 'close out', 'merge to main and clean up', 'session complete', 'wrap up this branch'.

2026-06-076

resolve-conflicts

navapbc/digital-service-orchestra

Use when the user is stuck in a merge conflict, rebase conflict, failed pull, or any git operation that left conflict markers in the working tree. Dispatches a conflict-analyzer sub-agent that classifies each conflicted hunk by confidence (auto-resolvable vs needs-human-review), auto-resolves high-confidence cases, validates the result, and rolls back if validation fails before falling through to human review. Trigger phrases include 'merge conflict', 'resolve conflicts', 'rebase conflict', 'git conflict', 'conflict markers', 'failed rebase', 'git pull conflict', 'fix the conflicts', 'help with this merge'.

2026-06-076

fp-recovery

navapbc/digital-service-orchestra

Manual review escalation when CI llm-review blocks a PR on a finding that looks like a false positive. Dispatches dso:code-reviewer-standard at opus tier on the PR's diff, parses the result, and emits a force-merge clearance when zero critical/important/fragile findings remain. Use ONLY when CI llm-review has failed on a suspect FP; not for routine PR shipping. Trigger phrases include 'force merge this PR', 'the CI review is wrong', 'false positive from llm-review', 'manual review override', 'FP recovery'.

2026-06-066

sprint

navapbc/digital-service-orchestra

Use when the user wants to execute an epic, run a sprint, work through a planned epic's stories and tasks, or coordinate multi-agent task execution end-to-end. Routes the epic by complexity (SIMPLE → direct implementation-plan, MODERATE → lightweight preplanning, COMPLEX → full preplanning), runs an SC-coverage gate at haiku/sonnet/opus tiers to confirm story coverage of epic success criteria, plans the task graph, dispatches sub-agents in batches with file-overlap and semantic-conflict checks, runs per-task review and post-batch validation (test gate, lint, AC verification, visual verification for UI), commits/pushes results, and verifies epic completion via the dso:completion-verifier agent before close. Trigger phrases include 'work the epic', 'execute the sprint', 'run the epic', 'sprint this epic', 'work through the stories', 'implement the planned tasks', 'kick off the sprint'.

2026-06-036

preplanning

navapbc/digital-service-orchestra

Use when breaking down an epic into user stories, story splitting, backlog grooming, defining acceptance criteria, or auditing and reconciling existing epic children before implementation. Dispatches an opus `dso:story-decomposer` sub-agent to draft prioritized vertical-slice user stories with measurable done definitions tied to epic Success Criteria (never inline), identifies dependencies, runs an adversarial red-team review pass, dispatches a UI designer for UI stories, and writes the story tickets to the tracker. Trigger phrases include 'break down this epic', 'split into stories', 'story splitting', 'backlog grooming', 'write user stories', 'define acceptance criteria', 'plan the epic', 'decompose the epic', 'reconcile epic children'.

2026-06-036

name	dso:test-quality-report
description	Surfaces calibration program health by running the monthly and quarterly calibration reports. Use when checking test-quality calibration trends, reviewing reviewer calibration data, or auditing the calibration program status. Trigger phrases include '/dso:test-quality-report', 'run calibration report', 'show calibration health', 'test quality report'.
user-invocable	true
allowed-tools	Bash, Read

Test Quality Report

Runs the calibration program health reports (monthly and quarterly) and surfaces their outputs.

Prerequisites

Calibration tracking tickets must exist. If they are absent, create them first:

bash .claude/scripts/dso-bootstrap-calibration-tickets.sh

Invocation

/dso:test-quality-report

Steps

Step 1: Run Monthly Report

.claude/scripts/dso calibration-report.sh monthly

Surface the full output to the user.

Step 2: Run Quarterly Report

.claude/scripts/dso calibration-report.sh quarterly

Surface the full output to the user.

Step 3: Summary

After both reports complete, provide a one-paragraph summary of the calibration program health, highlighting any trends, gaps, or action items surfaced by the reports.