What problem does it solve? After merging a PR, teams often lack a systematic way to confirm the change actually works in production. This Skill closes that gap by tracing the PR's code changes to the log signals they emit, querying production logs for those signals, and surfacing admin/support endpoints to verify state. ## Core Features & Use Cases - Work item ↔ PR resolution: Accepts a work item ID, PR ID, or URL and resolves the linked counterpart via GitHub Issues tools. - Change classification and signal mapping: Reads the PR diff, classifies changed files (controllers, services, data access, clients), and extracts entry points, log message templates, downstream calls, and data writes. - Tiered log verification: Runs scoped grep-based queries against console/local logs in four tiers — endpoint hits, new log emissions, errors from new code, and cross-service dependency checks — then compiles a structured verification report. - Use Case: After deploying a story that adds a new API endpoint, provide the PR number; the Skill identifies the new route and log statements, asks for a scoping identifier, queries the last 2 days of logs, and reports whether the endpoint was exercised cleanly. ## Quick Start Verify that PR 1234 is behaving correctly in production by checking its log signals over the past two days.
