[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2X8T87YHTQQTCSPR74TVX":3,"skill-same:01M6C2X8T87YHTQQTCSPR74TVX":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6C2X8T87YHTQQTCSPR74TVX","regression-report",null,"Generate comprehensive regression analysis reports combining bisect, baseline, and metrics data with actionable recommendations","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fregression-report\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41],"report","regression","regression report","generate","metrics","data","baseline","analysis","bisect","reports","recommendations","actionable","with","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: regression-report\nplatforms: [all]\ndescription: Generate comprehensive regression analysis reports combining bisect, baseline, and metrics data with actionable recommendations\n\n---\n\n# regression-report\n\nGenerate comprehensive regression analysis reports combining bisect, baseline, and metrics data.\n\n## Triggers\n\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"full regression report\" → comprehensive regression analysis\n- \"test health\" → regression summary report\n\n## Purpose\n\nThis skill produces comprehensive regression reports by:\n- Synthesizing data from bisect, baseline, and metrics\n- Correlating regressions with code changes\n- Identifying systemic issues and patterns\n- Providing actionable recommendations\n- Creating executive summaries\n- Supporting postmortem analysis\n\n## Behavior\n\nWhen triggered, this skill:\n\n1. **Gathers regression data**:\n   - Load bisect reports for root cause\n   - Import baseline comparison results\n   - Fetch regression metrics and trends\n   - Retrieve issue tracker data\n   - Collect CI\u002FCD logs\n\n2. **Correlates information**:\n   - Link regressions to code changes\n   - Map to requirements and features\n   - Identify common root causes\n   - Connect to team\u002Fcomponent ownership\n\n3. **Analyzes impact**:\n   - Assess user impact\n   - Calculate downtime\u002Fdegradation\n   - Measure business cost\n   - Evaluate reputation impact\n\n4. **Identifies patterns**:\n   - Recurring regression types\n   - High-risk components\n   - Time-based patterns\n   - Process gaps\n\n5. **Generates insights**:\n   - Root cause categories\n   - Prevention strategies\n   - Process improvements\n   - Tooling recommendations\n\n6. **Produces reports**:\n   - Executive summary\n   - Technical deep-dive\n   - Action plan\n   - Lessons learned\n\n## Report Types\n\n### Incident Report\n\n```yaml\nincident_report:\n  description: Single regression deep-dive\n  scope: One specific regression incident\n  audience: Technical team and stakeholders\n\n  sections:\n    - incident_summary\n    - timeline\n    - root_cause_analysis\n    - impact_assessment\n    - resolution_steps\n    - prevention_measures\n    - lessons_learned\n```\n\n### Sprint Regression Report\n\n```yaml\nsprint_report:\n  description: All regressions in a sprint\n  scope: Sprint boundary\n  audience: Development team\n\n  sections:\n    - sprint_summary\n    - regression_list\n    - metrics_summary\n    - hotspot_analysis\n    - recommendations\n    - goals_for_next_sprint\n```\n\n### Release Regression Report\n\n```yaml\nrelease_report:\n  description: Regression analysis for release\n  scope: Release cycle\n  audience: Release management and stakeholders\n\n  sections:\n    - release_summary\n    - regression_timeline\n    - escape_analysis\n    - quality_gates_review\n    - lessons_learned\n    - release_readiness\n```\n\n### Quarterly Regression Analysis\n\n```yaml\nquarterly_report:\n  description: Strategic regression analysis\n  scope: 3 months\n  audience: Leadership and engineering managers\n\n  sections:\n    - executive_summary\n    - trend_analysis\n    - strategic_insights\n    - investment_recommendations\n    - process_improvements\n    - success_metrics\n```\n\n## Comprehensive Report Format\n\n```markdown\n# Comprehensive Regression Report\n\n**Period**: Sprint 13 (2026-01-14 to 2026-01-28)\n**Project**: User Service\n**Report Type**: Sprint Regression Analysis\n**Generated**: 2026-01-28 17:00:00\n**Analyzer**: regression-report skill\n\n---\n\n## Executive Summary\n\n**Overall Assessment**: ⚠️ Acceptable Quality with Concerns\n\n| Metric | Value | Status |\n|--------|-------|--------|\n| Regressions Detected | 4 | ✅ Within target (\u003C 5) |\n| Production Escapes | 1 | ⚠️ Above target (0 preferred) |\n| Mean Time to Detect | 8.5h | ✅ Excellent |\n| Mean Time to Fix | 18.7h | ⚠️ Close to target |\n| User Impact | 500 users | ⚠️ Medium |\n\n**Key Findings**:\n- Regression rate within acceptable range but auth module concerning\n- One production escape indicates staging test gap\n- Detection speed excellent, fix time acceptable\n- Systemic issue: Integration testing coverage insufficient\n\n**Priority Actions**:\n1. Add integration tests for authentication flows\n2. Improve staging environment test coverage\n3. Implement regression test requirement for all fixes\n\n---\n\n## Regression Inventory\n\n### REG-001: JWT Issuer Validation Breaks Existing Sessions\n\n**Severity**: High\n**Status**: Fixed (deployed 2026-01-16)\n**Detection**: Automated test failure\n**Environment**: Staging\n\n**Timeline**:\n- 2026-01-15 14:32: Breaking commit merged (pqr901)\n- 2026-01-15 16:15: CI test failure detected (2h MTTD)\n- 2026-01-15 18:45: Root cause identified via bisect\n- 2026-01-16 09:30: Fix deployed (15h MTTF)\n\n**Root Cause**: Required `iss` claim in JWT validation without backward compatibility\n\n**Impact**: All existing user sessions invalidated\n\n**Files Changed**:\n- src\u002Fauth\u002Fvalidate-token.ts (+15\u002F-5)\n- src\u002Fauth\u002Fgenerate-token.ts (+8\u002F-2)\n\n**Fix**: Added feature flag for gradual rollout\n\n**Prevention**:\n- [ ] Add integration tests for auth changes\n- [ ] Require backward compatibility review\n\n**References**:\n- Bisect Report: @.aiwg\u002Ftesting\u002Fregression-bisect-jwt.md\n- Issue: #456\n- PR: #789\n\n---\n\n### REG-002: User Profile Update Returns 500 on Invalid Email\n\n**Severity**: Critical\n**Status**: Fixed (deployed 2026-01-18)\n**Detection**: Production monitoring\n**Environment**: Production\n\n**Timeline**:\n- 2026-01-17 08:00: Deployed to production\n- 2026-01-17 20:15: Error spike detected (12h MTTD)\n- 2026-01-18 02:30: Root cause identified\n- 2026-01-18 04:15: Hotfix deployed (8h MTTF)\n\n**Root Cause**: Validation middleware error handling broken, returns 500 instead of 400\n\n**Impact**:\n- 500 users affected\n- 45 support tickets\n- 12 hours partial service degradation\n\n**Files Changed**:\n- src\u002Fapi\u002Fvalidation-middleware.ts (+3\u002F-8)\n\n**Cost**:\n- Engineering: 8 hours incident response\n- Support: 12 hours ticket triage\n- Reputation: Customer satisfaction impact\n\n**Fix**: Restored proper error handling\n\n**Prevention**:\n- [ ] Add error code validation tests\n- [ ] Improve staging test coverage\n- [ ] Add monitoring for error rate spikes\n\n**References**:\n- Incident Report: @.aiwg\u002Fincidents\u002FINC-2026-001.md\n- Issue: #478\n- Hotfix PR: #791\n\n---\n\n### REG-003: Password Reset Email Fails for Gmail Users\n\n**Severity**: Medium\n**Status**: Fixed (deployed 2026-01-22)\n**Detection**: Manual QA testing\n**Environment**: Staging\n\n**Timeline**:\n- 2026-01-20 11:00: Code merged\n- 2026-01-21 15:30: QA detected (28.5h MTTD)\n- 2026-01-22 10:00: Fix deployed (18.5h MTTF)\n\n**Root Cause**: Email template contained invalid HTML characters rejected by Gmail\n\n**Impact**: Password reset broken for ~40% of user base (Gmail users)\n\n**Files Changed**:\n- templates\u002Femail\u002Fpassword-reset.html (+5\u002F-3)\n\n**Fix**: HTML entity encoding for special characters\n\n**Prevention**:\n- [ ] Add email template validation\n- [ ] Test with multiple email providers\n- [ ] Add email delivery monitoring\n\n**References**:\n- Issue: #482\n- PR: #794\n\n---\n\n### REG-004: Dashboard Widget Load Time Increased\n\n**Severity**: Low\n**Status**: Fixed (deployed 2026-01-26)\n**Detection**: Performance baseline comparison\n**Environment**: Staging\n\n**Timeline**:\n- 2026-01-24 09:00: Performance test detected slowdown\n- 2026-01-24 10:15: Root cause identified (1.25h MTTD)\n- 2026-01-26 08:00: Optimization deployed (45.75h MTTF)\n\n**Root Cause**: N+1 query introduced in dashboard widget\n\n**Impact**: Dashboard load time increased from 0.8s to 2.3s\n\n**Files Changed**:\n- src\u002Fdashboard\u002Fwidgets\u002Factivity-feed.ts (+12\u002F-5)\n\n**Fix**: Added eager loading to eliminate N+1\n\n**Prevention**:\n- [ ] Add performance regression tests\n- [ ] Code review focus on query optimization\n\n**References**:\n- Baseline Comparison: @.aiwg\u002Ftesting\u002Fbaseline-comparison-perf.md\n- Issue: #485\n- PR: #797\n\n---\n\n## Impact Analysis\n\n### User Impact\n\n| Regression | Users Affected | Duration | Severity |\n|------------|----------------|----------|----------|\n| REG-001 | 0 (staging) | N\u002FA | High (avoided) |\n| REG-002 | 500 | 12h | Critical |\n| REG-003 | 0 (staging) | N\u002FA | Medium (avoided) |\n| REG-004 | 0 (staging) | N\u002FA | Low (avoided) |\n\n**Total Production Impact**: 500 users, 12 hours\n**Escapes Prevented**: 3 of 4 regressions caught pre-production\n\n### Business Impact\n\n```\nDirect Costs:\n- Engineering incident response: 24 hours @ $150\u002Fh = $3,600\n- Support ticket triage: 12 hours @ $75\u002Fh = $900\nTotal Direct: $4,500\n\nIndirect Costs:\n- Customer satisfaction impact (estimated)\n- Reputation damage (1 production incident)\n- Lost productivity (500 users × 12h)\nEstimated Indirect: $8,000\n\nTotal Estimated Cost: $12,500\n```\n\n### Component Impact\n\n| Component | Regressions | User Impact | Risk Level |\n|-----------|-------------|-------------|------------|\n| src\u002Fauth\u002F | 1 | High (avoided) | ? High |\n| src\u002Fapi\u002F | 1 | Critical (500 users) | ? High |\n| templates\u002F | 1 | Medium (avoided) | ? Medium |\n| src\u002Fdashboard\u002F | 1 | Low (avoided) | ? Low |\n\n**High-Risk Components**: Auth and API modules require increased testing\n\n---\n\n## Root Cause Analysis\n\n### Root Cause Categories\n\n| Category | Count | % | Examples |\n|----------|-------|---|----------|\n| Missing integration tests | 2 | 50% | REG-001, REG-002 |\n| Missing validation | 1 | 25% | REG-003 |\n| Performance not tested | 1 | 25% | REG-004 |\n\n**Systemic Issue**: Integration testing coverage insufficient (50% of regressions)\n\n### Prevention Success Rate\n\n| Prevention Measure | Present? | Effective? |\n|-------------------|----------|------------|\n| Unit tests | ✅ Yes | ⚠️ Partial |\n| Integration tests | ❌ No | N\u002FA |\n| Performance tests | ⚠️ Partial | ⚠️ Partial |\n| Email validation | ❌ No | N\u002FA |\n| Staging environment | ✅ Yes | ✅ Yes (caught 3\u002F4) |\n\n**Gap**: Integration tests would have prevented 50% of regressions\n\n---\n\n## Metrics Summary\n\n### Sprint Performance\n\n| Metric | Sprint 13 | Sprint 12 | Change |\n|--------|-----------|-----------|--------|\n| Regressions | 4 | 4 | → Stable |\n| MTTD | 8.5h | 12h | ↓ Improved |\n| MTTF | 18.7h | 28.4h | ↓ Improved |\n| Escape Rate | 25% (1\u002F4) | 0% | ↑ Worsened |\n\n**Trend**: Detection and fix times improving, but production escape concerning\n\n### Quality Gates\n\n| Gate | Target | Actual | Status |\n|------|--------|--------|--------|\n| Unit test coverage | 80% | 85% | ✅ Pass |\n| Integration test coverage | 60% | 42% | ❌ Fail |\n| Performance baseline | No degradation | 1 regression | ⚠️ Warning |\n| Security scan | No critical | Pass | ✅ Pass |\n\n**Failed Gate**: Integration test coverage below target\n\n---\n\n## Recommendations\n\n### Immediate (This Week)\n\n**Priority 1: Add Integration Tests for Auth**\n- Reason: 1 auth regression, staging escape\n- Impact: Prevent auth-related regressions\n- Effort: 2 days\n- Owner: Test Engineer\n- Target: +20% integration coverage\n\n**Priority 2: Fix Email Template Validation**\n- Reason: REG-003 could have been automated\n- Impact: Catch email issues pre-deployment\n- Effort: 1 day\n- Owner: DevOps Engineer\n\n**Priority 3: Implement Regression Test Requirement**\n- Reason: 25% recurrence rate on fixes without tests\n- Impact: Prevent regression recurrence\n- Effort: Process change (1 hour)\n- Owner: Tech Lead\n\n### Short-term (This Sprint)\n\n**Priority 4: Improve Staging Test Coverage**\n- Reason: Production escape indicates gap\n- Impact: Reduce escape rate to \u003C5%\n- Effort: 1 week\n- Owner: Test Architect\n\n**Priority 5: Add Performance Regression Tests**\n- Reason: REG-004 caught late\n- Impact: Earlier performance issue detection\n- Effort: 3 days\n- Owner: Performance Engineer\n\n**Priority 6: Review Error Handling Standards**\n- Reason: REG-002 returned 500 instead of 400\n- Impact: Consistent error behavior\n- Effort: 2 days (review + guidelines)\n- Owner: API Designer\n\n### Ongoing\n\n**Priority 7: Require Integration Tests for Auth PRs**\n- Reason: Auth module high-risk\n- Impact: No auth regressions without tests\n- Effort: PR template update\n- Owner: Tech Lead\n\n**Priority 8: Weekly Regression Review**\n- Reason: Early pattern identification\n- Impact: Faster response to trends\n- Effort: 30 min\u002Fweek\n- Owner: Test Lead\n\n---\n\n## Lessons Learned\n\n### What Went Well\n\n1. **Fast Detection**: MTTD of 8.5h shows automation working\n2. **Staging Environment**: Caught 3 of 4 regressions before production\n3. **Bisect Tooling**: Root cause identification very fast\n4. **Team Response**: Fast fix times (18.7h MTTF)\n\n### What Didn't Go Well\n\n1. **Production Escape**: REG-002 bypassed all pre-production testing\n2. **Integration Coverage**: Too low to catch cross-component issues\n3. **Email Validation**: No automated testing for email templates\n4. **Backward Compatibility**: REG-001 broke existing sessions\n\n### Process Improvements\n\n| Issue | Improvement | Timeline |\n|-------|-------------|----------|\n| Production escape | Add integration test gates | This sprint |\n| Missing email validation | Automate template testing | This sprint |\n| Auth regressions | Require integration tests | Immediate |\n| Performance regressions | Add performance baselines | Next sprint |\n\n---\n\n## Sprint Goals for Sprint 14\n\nBased on this analysis, Sprint 14 regression goals:\n\n| Goal | Target | Success Criteria |\n|------|--------|------------------|\n| Regression Rate | \u003C 4 | Fewer total regressions |\n| Integration Coverage | 60% | Meet quality gate |\n| Escape Rate | 0% | No production regressions |\n| MTTD | \u003C 8h | Maintain current level |\n| MTTF | \u003C 18h | Slightly faster fixes |\n\n**Focus Areas**: Integration testing, staging coverage, auth module\n\n---\n\n## Appendices\n\n### A. Regression Timeline\n\n```\n2026-01-15: REG-001 introduced (auth JWT)\n2026-01-15: REG-001 detected (2h)\n2026-01-16: REG-001 fixed (15h)\n2026-01-17: REG-002 introduced (validation)\n2026-01-17: REG-002 escaped to production\n2026-01-18: REG-002 detected (12h)\n2026-01-18: REG-002 fixed (8h)\n2026-01-20: REG-003 introduced (email)\n2026-01-21: REG-003 detected (28.5h)\n2026-01-22: REG-003 fixed (18.5h)\n2026-01-24: REG-004 introduced (performance)\n2026-01-24: REG-004 detected (1.25h)\n2026-01-26: REG-004 fixed (45.75h)\n```\n\n### B. References\n\n- Bisect Reports: @.aiwg\u002Ftesting\u002Fregression-bisect-*\u002F\n- Baseline Comparisons: @.aiwg\u002Ftesting\u002Fbaseline-comparisons\u002F\n- Metrics Dashboard: @.aiwg\u002Ftesting\u002Fregression-metrics-dashboard.md\n- Incident Reports: @.aiwg\u002Fincidents\u002F\n- Issues: GitHub Issues (label: regression)\n\n### C. Data Sources\n\n- Regression test results: `.aiwg\u002Ftesting\u002Fregression-results\u002F`\n- CI\u002FCD logs: GitHub Actions\n- Issue tracker: GitHub Issues\n- Monitoring: Datadog\n- User reports: Support tickets\n```\n\n## Usage Examples\n\n### Generate Sprint Report\n\n```\nUser: \"Generate regression report for this sprint\"\n\nSkill executes:\n1. Identify sprint boundary (Sprint 13)\n2. Collect all regression data\n3. Correlate with code changes\n4. Analyze patterns and impact\n5. Generate recommendations\n\nOutput:\n\"Sprint Regression Report Generated\n\nSprint 13 Summary:\n- 4 regressions detected\n- 1 production escape\n- 8.5h MTTD, 18.7h MTTF\n- 500 users impacted\n\nKey Findings:\n- Integration testing gap (50% of regressions)\n- Auth module high-risk (needs attention)\n- Staging caught 75% (good)\n\nTop Recommendations:\n1. Add integration tests for auth\n2. Improve staging coverage\n3. Require regression tests for fixes\n\nFull report: .aiwg\u002Ftesting\u002Fregression-report-sprint-13.md\"\n```\n\n### Incident Postmortem\n\n```\nUser: \"Regression report for the validation incident\"\n\nSkill analyzes:\n- REG-002 incident data\n- Timeline and impact\n- Root cause from bisect\n- Related regressions\n\nOutput:\n\"Incident Postmortem: REG-002\n\nTimeline: 12 hours (detection to fix)\nImpact: 500 users, 45 support tickets\nCost: ~$12,500 (direct + indirect)\n\nRoot Cause: Validation middleware broken\nPrevention: Integration tests missing\n\nRecommendations:\n- Add error code validation tests\n- Improve staging coverage\n- Add monitoring for error spikes\n\nLessons Learned:\n- Fast response (8h MTTF)\n- Staging gap allowed escape\n- Need integration test gate\n\nFull postmortem: .aiwg\u002Ftesting\u002Fregression-postmortem-REG-002.md\"\n```\n\n### Quarterly Analysis\n\n```\nUser: \"Quarterly regression analysis\"\n\nSkill generates:\n\"Quarterly Regression Analysis (Q1 2026)\n\nExecutive Summary:\n- 58 total regressions (-35% vs Q4 2025)\n- 3 production escapes (-70% vs Q4)\n- MTTD: 9.2h (↓ from 24h)\n- MTTF: 22h (↓ from 42h)\n\nStrategic Insights:\n- Automation investment paying off (76% faster detection)\n- Integration testing gap remains (40% of regressions)\n- Auth and API modules highest risk\n\nInvestment Recommendations:\n- $50k: Integration test automation\n- $30k: Performance testing platform\n- $20k: Staging environment expansion\n\nFull analysis: .aiwg\u002Ftesting\u002Fregression-analysis-Q1-2026.md\"\n```\n\n## Integration\n\nThis skill uses:\n- `regression-bisect`: Import root cause analysis\n- `regression-baseline`: Import drift data\n- `regression-metrics`: Import statistical trends\n- `project-awareness`: Detect sprints\u002Freleases\n- `traceability-check`: Link to requirements\n\n## Agent Orchestration\n\n```yaml\nagents:\n  synthesis:\n    agent: technical-writer\n    focus: Report generation and clarity\n\n  analysis:\n    agent: metrics-analyst\n    focus: Data correlation and insights\n\n  recommendations:\n    agent: test-architect\n    focus: Prevention strategies\n```\n\n## Configuration\n\n### Report Templates\n\n```yaml\nreport_templates:\n  incident:\n    template: templates\u002Fregression\u002Fincident-report.md\n    sections: [summary, timeline, root_cause, impact, prevention]\n\n  sprint:\n    template: templates\u002Fregression\u002Fsprint-report.md\n    sections: [summary, inventory, metrics, recommendations]\n\n  quarterly:\n    template: templates\u002Fregression\u002Fquarterly-report.md\n    sections: [executive, trends, strategic, investments]\n```\n\n### Data Aggregation\n\n```yaml\naggregation_config:\n  sources:\n    - bisect_reports: .aiwg\u002Ftesting\u002Fregression-bisect-*\u002F\n    - baselines: .aiwg\u002Ftesting\u002Fbaseline-comparisons\u002F\n    - metrics: .aiwg\u002Ftesting\u002Fregression-metrics-dashboard.md\n    - issues: github_issues\n    - incidents: .aiwg\u002Fincidents\u002F\n\n  correlation_rules:\n    - link_bisect_to_issue\n    - map_component_to_owner\n    - calculate_business_impact\n```\n\n## Output Locations\n\n- Reports: `.aiwg\u002Ftesting\u002Fregression-report-{period}.md`\n- Postmortems: `.aiwg\u002Ftesting\u002Fregression-postmortem-{issue}.md`\n- Quarterly: `.aiwg\u002Ftesting\u002Fregression-analysis-Q{n}-{year}.md`\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fschemas\u002Ftest\u002Fregression-report-schema.yaml\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fregression\u002Fincident-report.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Ftechnical-writer.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fmetrics-analyst.md\n","# regression-report\n\nGenerate comprehensive regression analysis reports combining bisect, baseline, and metrics data.\n\n## Triggers\n\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"full regression report\" → comprehensive regression analysis\n- \"test health\" → regression summary report\n\n## Purpose\n\nThis skill produces comprehensive regression reports by:\n- Synthesizing data from bisect, baseline, and metrics\n- Correlating regressions with code changes\n- Identifying systemic issues and patterns\n- Providing actionable recommendations\n- Creating executive summaries\n- Supporting postmortem analysis\n\n## Behavior\n\nWhen triggered, this skill:\n\n1. **Gathers regression data**:\n   - Load bisect reports for root cause\n   - Import baseline comparison results\n   - Fetch regression metrics and trends\n   - Retrieve issue tracker data\n   - Collect CI\u002FCD logs\n\n2. **Correlates information**:\n   - Link regressions to code changes\n   - Map to requirements and features\n   - Identify common root causes\n   - Connect to team\u002Fcomponent ownership\n\n3. **Analyzes impact**:\n   - Assess user impact\n   - Calculate downtime\u002Fdegradation\n   - Measure business cost\n   - Evaluate reputation impact\n\n4. **Identifies patterns**:\n   - Recurring regression types\n   - High-risk components\n   - Time-based patterns\n   - Process gaps\n\n5. **Generates insights**:\n   - Root cause categories\n   - Prevention strategies\n   - Process improvements\n   - Tooling recommendations\n\n6. **Produces reports**:\n   - Executive summary\n   - Technical deep-dive\n   - Action plan\n   - Lessons learned\n\n## Report Types\n\n### Incident Report\n\n```yaml\nincident_report:\n  description: Single regression deep-dive\n  scope: One specific regression incident\n  audience: Technical team and stakeholders\n\n  sections:\n    - incident_summary\n    - timeline\n    - root_cause_analysis\n    - impact_assessment\n    - resolution_steps\n    - prevention_measures\n    - lessons_learned\n```\n\n### Sprint Regression Report\n\n```yaml\nsprint_report:\n  description: All regressions in a sprint\n  scope: Sprint boundary\n  audience: Development team\n\n  sections:\n    - sprint_summary\n    - regression_list\n    - metrics_summary\n    - hotspot_analysis\n    - recommendations\n    - goals_for_next_sprint\n```\n\n### Release Regression Report\n\n```yaml\nrelease_report:\n  description: Regression analysis for release\n  scope: Release cycle\n  audience: Release management and stakeholders\n\n  sections:\n    - release_summary\n    - regression_timeline\n    - escape_analysis\n    - quality_gates_review\n    - lessons_learned\n    - release_readiness\n```\n\n### Quarterly Regression Analysis\n\n```yaml\nquarterly_report:\n  description: Strategic regression analysis\n  scope: 3 months\n  audience: Leadership and engineering managers\n\n  sections:\n    - executive_summary\n    - trend_analysis\n    - strategic_insights\n    - investment_recommendations\n    - process_improvements\n    - success_metrics\n```\n\n## Comprehensive Report Format\n\n```markdown\n# Comprehensive Regression Report\n\n**Period**: Sprint 13 (2026-01-14 to 2026-01-28)\n**Project**: User Service\n**Report Type**: Sprint Regression Analysis\n**Generated**: 2026-01-28 17:00:00\n**Analyzer**: regression-report skill\n\n---\n\n## Executive Summary\n\n**Overall Assessment**: ⚠️ Acceptable Quality with Concerns\n\n| Metric | Value | Status |\n|--------|-------|--------|\n| Regressions Detected | 4 | ✅ Within target (\u003C 5) |\n| Production Escapes | 1 | ⚠️ Above target (0 preferred) |\n| Mean Time to Detect | 8.5h | ✅ Excellent |\n| Mean Time to Fix | 18.7h | ⚠️ Close to target |\n| User Impact | 500 users | ⚠️ Medium |\n\n**Key Findings**:\n- Regression rate within acceptable range but auth module concerning\n- One production escape indicates staging test gap\n- Detection speed excellent, fix time acceptable\n- Systemic issue: Integration testing coverage insufficient\n\n**Priority Actions**:\n1. Add integration tests for authentication flows\n2. Improve staging environment test coverage\n3. Implement regression test requirement for all fixes\n\n---\n\n## Regression Inventory\n\n### REG-001: JWT Issuer Validation Breaks Existing Sessions\n\n**Severity**: High\n**Status**: Fixed (deployed 2026-01-16)\n**Detection**: Automated test failure\n**Environment**: Staging\n\n**Timeline**:\n- 2026-01-15 14:32: Breaking commit merged (pqr901)\n- 2026-01-15 16:15: CI test failure detected (2h MTTD)\n- 2026-01-15 18:45: Root cause identified via bisect\n- 2026-01-16 09:30: Fix deployed (15h MTTF)\n\n**Root Cause**: Required `iss` claim in JWT validation without backward compatibility\n\n**Impact**: All existing user sessions invalidated\n\n**Files Changed**:\n- src\u002Fauth\u002Fvalidate-token.ts (+15\u002F-5)\n- src\u002Fauth\u002Fgenerate-token.ts (+8\u002F-2)\n\n**Fix**: Added feature flag for gradual rollout\n\n**Prevention**:\n- [ ] Add integration tests for auth changes\n- [ ] Require backward compatibility review\n\n**References**:\n- Bisect Report: @.aiwg\u002Ftesting\u002Fregression-bisect-jwt.md\n- Issue: #456\n- PR: #789\n\n---\n\n### REG-002: User Profile Update Returns 500 on Invalid Email\n\n**Severity**: Critical\n**Status**: Fixed (deployed 2026-01-18)\n**Detection**: Production monitoring\n**Environment**: Production\n\n**Timeline**:\n- 2026-01-17 08:00: Deployed to production\n- 2026-01-17 20:15: Error spike detected (12h MTTD)\n- 2026-01-18 02:30: Root cause identified\n- 2026-01-18 04:15: Hotfix deployed (8h MTTF)\n\n**Root Cause**: Validation middleware error handling broken, returns 500 instead of 400\n\n**Impact**:\n- 500 users affected\n- 45 support tickets\n- 12 hours partial service degradation\n\n**Files Changed**:\n- src\u002Fapi\u002Fvalidation-middleware.ts (+3\u002F-8)\n\n**Cost**:\n- Engineering: 8 hours incident response\n- Support: 12 hours ticket triage\n- Reputation: Customer satisfaction impact\n\n**Fix**: Restored proper error handling\n\n**Prevention**:\n- [ ] Add error code validation tests\n- [ ] Improve staging test coverage\n- [ ] Add monitoring for error rate spikes\n\n**References**:\n- Incident Report: @.aiwg\u002Fincidents\u002FINC-2026-001.md\n- Issue: #478\n- Hotfix PR: #791\n\n---\n\n### REG-003: Password Reset Email Fails for Gmail Users\n\n**Severity**: Medium\n**Status**: Fixed (deployed 2026-01-22)\n**Detection**: Manual QA testing\n**Environment**: Staging\n\n**Timeline**:\n- 2026-01-20 11:00: Code merged\n- 2026-01-21 15:30: QA detected (28.5h MTTD)\n- 2026-01-22 10:00: Fix deployed (18.5h MTTF)\n\n**Root Cause**: Email template contained invalid HTML characters rejected by Gmail\n\n**Impact**: Password reset broken for ~40% of user base (Gmail users)\n\n**Files Changed**:\n- templates\u002Femail\u002Fpassword-reset.html (+5\u002F-3)\n\n**Fix**: HTML entity encoding for special characters\n\n**Prevention**:\n- [ ] Add email template validation\n- [ ] Test with multiple email providers\n- [ ] Add email delivery monitoring\n\n**References**:\n- Issue: #482\n- PR: #794\n\n---\n\n### REG-004: Dashboard Widget Load Time Increased\n\n**Severity**: Low\n**Status**: Fixed (deployed 2026-01-26)\n**Detection**: Performance baseline comparison\n**Environment**: Staging\n\n**Timeline**:\n- 2026-01-24 09:00: Performance test detected slowdown\n- 2026-01-24 10:15: Root cause identified (1.25h MTTD)\n- 2026-01-26 08:00: Optimization deployed (45.75h MTTF)\n\n**Root Cause**: N+1 query introduced in dashboard widget\n\n**Impact**: Dashboard load time increased from 0.8s to 2.3s\n\n**Files Changed**:\n- src\u002Fdashboard\u002Fwidgets\u002Factivity-feed.ts (+12\u002F-5)\n\n**Fix**: Added eager loading to eliminate N+1\n\n**Prevention**:\n- [ ] Add performance regression tests\n- [ ] Code review focus on query optimization\n\n**References**:\n- Baseline Comparison: @.aiwg\u002Ftesting\u002Fbaseline-comparison-perf.md\n- Issue: #485\n- PR: #797\n\n---\n\n## Impact Analysis\n\n### User Impact\n\n| Regression | Users Affected | Duration | Severity |\n|------------|----------------|----------|----------|\n| REG-001 | 0 (staging) | N\u002FA | High (avoided) |\n| REG-002 | 500 | 12h | Critical |\n| REG-003 | 0 (staging) | N\u002FA | Medium (avoided) |\n| REG-004 | 0 (staging) | N\u002FA | Low (avoided) |\n\n**Total Production Impact**: 500 users, 12 hours\n**Escapes Prevented**: 3 of 4 regressions caught pre-production\n\n### Business Impact\n\n```\nDirect Costs:\n- Engineering incident response: 24 hours @ $150\u002Fh = $3,600\n- Support ticket triage: 12 hours @ $75\u002Fh = $900\nTotal Direct: $4,500\n\nIndirect Costs:\n- Customer satisfaction impact (estimated)\n- Reputation damage (1 production incident)\n- Lost productivity (500 users × 12h)\nEstimated Indirect: $8,000\n\nTotal Estimated Cost: $12,500\n```\n\n### Component Impact\n\n| Component | Regressions | User Impact | Risk Level |\n|-----------|-------------|-------------|------------|\n| src\u002Fauth\u002F | 1 | High (avoided) | ? High |\n| src\u002Fapi\u002F | 1 | Critical (500 users) | ? High |\n| templates\u002F | 1 | Medium (avoided) | ? Medium |\n| src\u002Fdashboard\u002F | 1 | Low (avoided) | ? Low |\n\n**High-Risk Components**: Auth and API modules require increased testing\n\n---\n\n## Root Cause Analysis\n\n### Root Cause Categories\n\n| Category | Count | % | Examples |\n|----------|-------|---|----------|\n| Missing integration tests | 2 | 50% | REG-001, REG-002 |\n| Missing validation | 1 | 25% | REG-003 |\n| Performance not tested | 1 | 25% | REG-004 |\n\n**Systemic Issue**: Integration testing coverage insufficient (50% of regressions)\n\n### Prevention Success Rate\n\n| Prevention Measure | Present? | Effective? |\n|-------------------|----------|------------|\n| Unit tests | ✅ Yes | ⚠️ Partial |\n| Integration tests | ❌ No | N\u002FA |\n| Performance tests | ⚠️ Partial | ⚠️ Partial |\n| Email validation | ❌ No | N\u002FA |\n| Staging environment | ✅ Yes | ✅ Yes (caught 3\u002F4) |\n\n**Gap**: Integration tests would have prevented 50% of regressions\n\n---\n\n## Metrics Summary\n\n### Sprint Performance\n\n| Metric | Sprint 13 | Sprint 12 | Change |\n|--------|-----------|-----------|--------|\n| Regressions | 4 | 4 | → Stable |\n| MTTD | 8.5h | 12h | ↓ Improved |\n| MTTF | 18.7h | 28.4h | ↓ Improved |\n| Escape Rate | 25% (1\u002F4) | 0% | ↑ Worsened |\n\n**Trend**: Detection and fix times improving, but production escape concerning\n\n### Quality Gates\n\n| Gate | Target | Actual | Status |\n|------|--------|--------|--------|\n| Unit test coverage | 80% | 85% | ✅ Pass |\n| Integration test coverage | 60% | 42% | ❌ Fail |\n| Performance baseline | No degradation | 1 regression | ⚠️ Warning |\n| Security scan | No critical | Pass | ✅ Pass |\n\n**Failed Gate**: Integration test coverage below target\n\n---\n\n## Recommendations\n\n### Immediate (This Week)\n\n**Priority 1: Add Integration Tests for Auth**\n- Reason: 1 auth regression, staging escape\n- Impact: Prevent auth-related regressions\n- Effort: 2 days\n- Owner: Test Engineer\n- Target: +20% integration coverage\n\n**Priority 2: Fix Email Template Validation**\n- Reason: REG-003 could have been automated\n- Impact: Catch email issues pre-deployment\n- Effort: 1 day\n- Owner: DevOps Engineer\n\n**Priority 3: Implement Regression Test Requirement**\n- Reason: 25% recurrence rate on fixes without tests\n- Impact: Prevent regression recurrence\n- Effort: Process change (1 hour)\n- Owner: Tech Lead\n\n### Short-term (This Sprint)\n\n**Priority 4: Improve Staging Test Coverage**\n- Reason: Production escape indicates gap\n- Impact: Reduce escape rate to \u003C5%\n- Effort: 1 week\n- Owner: Test Architect\n\n**Priority 5: Add Performance Regression Tests**\n- Reason: REG-004 caught late\n- Impact: Earlier performance issue detection\n- Effort: 3 days\n- Owner: Performance Engineer\n\n**Priority 6: Review Error Handling Standards**\n- Reason: REG-002 returned 500 instead of 400\n- Impact: Consistent error behavior\n- Effort: 2 days (review + guidelines)\n- Owner: API Designer\n\n### Ongoing\n\n**Priority 7: Require Integration Tests for Auth PRs**\n- Reason: Auth module high-risk\n- Impact: No auth regressions without tests\n- Effort: PR template update\n- Owner: Tech Lead\n\n**Priority 8: Weekly Regression Review**\n- Reason: Early pattern identification\n- Impact: Faster response to trends\n- Effort: 30 min\u002Fweek\n- Owner: Test Lead\n\n---\n\n## Lessons Learned\n\n### What Went Well\n\n1. **Fast Detection**: MTTD of 8.5h shows automation working\n2. **Staging Environment**: Caught 3 of 4 regressions before production\n3. **Bisect Tooling**: Root cause identification very fast\n4. **Team Response**: Fast fix times (18.7h MTTF)\n\n### What Didn't Go Well\n\n1. **Production Escape**: REG-002 bypassed all pre-production testing\n2. **Integration Coverage**: Too low to catch cross-component issues\n3. **Email Validation**: No automated testing for email templates\n4. **Backward Compatibility**: REG-001 broke existing sessions\n\n### Process Improvements\n\n| Issue | Improvement | Timeline |\n|-------|-------------|----------|\n| Production escape | Add integration test gates | This sprint |\n| Missing email validation | Automate template testing | This sprint |\n| Auth regressions | Require integration tests | Immediate |\n| Performance regressions | Add performance baselines | Next sprint |\n\n---\n\n## Sprint Goals for Sprint 14\n\nBased on this analysis, Sprint 14 regression goals:\n\n| Goal | Target | Success Criteria |\n|------|--------|------------------|\n| Regression Rate | \u003C 4 | Fewer total regressions |\n| Integration Coverage | 60% | Meet quality gate |\n| Escape Rate | 0% | No production regressions |\n| MTTD | \u003C 8h | Maintain current level |\n| MTTF | \u003C 18h | Slightly faster fixes |\n\n**Focus Areas**: Integration testing, staging coverage, auth module\n\n---\n\n## Appendices\n\n### A. Regression Timeline\n\n```\n2026-01-15: REG-001 introduced (auth JWT)\n2026-01-15: REG-001 detected (2h)\n2026-01-16: REG-001 fixed (15h)\n2026-01-17: REG-002 introduced (validation)\n2026-01-17: REG-002 escaped to production\n2026-01-18: REG-002 detected (12h)\n2026-01-18: REG-002 fixed (8h)\n2026-01-20: REG-003 introduced (email)\n2026-01-21: REG-003 detected (28.5h)\n2026-01-22: REG-003 fixed (18.5h)\n2026-01-24: REG-004 introduced (performance)\n2026-01-24: REG-004 detected (1.25h)\n2026-01-26: REG-004 fixed (45.75h)\n```\n\n### B. References\n\n- Bisect Reports: @.aiwg\u002Ftesting\u002Fregression-bisect-*\u002F\n- Baseline Comparisons: @.aiwg\u002Ftesting\u002Fbaseline-comparisons\u002F\n- Metrics Dashboard: @.aiwg\u002Ftesting\u002Fregression-metrics-dashboard.md\n- Incident Reports: @.aiwg\u002Fincidents\u002F\n- Issues: GitHub Issues (label: regression)\n\n### C. Data Sources\n\n- Regression test results: `.aiwg\u002Ftesting\u002Fregression-results\u002F`\n- CI\u002FCD logs: GitHub Actions\n- Issue tracker: GitHub Issues\n- Monitoring: Datadog\n- User reports: Support tickets\n```\n\n## Usage Examples\n\n### Generate Sprint Report\n\n```\nUser: \"Generate regression report for this sprint\"\n\nSkill executes:\n1. Identify sprint boundary (Sprint 13)\n2. Collect all regression data\n3. Correlate with code changes\n4. Analyze patterns and impact\n5. Generate recommendations\n\nOutput:\n\"Sprint Regression Report Generated\n\nSprint 13 Summary:\n- 4 regressions detected\n- 1 production escape\n- 8.5h MTTD, 18.7h MTTF\n- 500 users impacted\n\nKey Findings:\n- Integration testing gap (50% of regressions)\n- Auth module high-risk (needs attention)\n- Staging caught 75% (good)\n\nTop Recommendations:\n1. Add integration tests for auth\n2. Improve staging coverage\n3. Require regression tests for fixes\n\nFull report: .aiwg\u002Ftesting\u002Fregression-report-sprint-13.md\"\n```\n\n### Incident Postmortem\n\n```\nUser: \"Regression report for the validation incident\"\n\nSkill analyzes:\n- REG-002 incident data\n- Timeline and impact\n- Root cause from bisect\n- Related regressions\n\nOutput:\n\"Incident Postmortem: REG-002\n\nTimeline: 12 hours (detection to fix)\nImpact: 500 users, 45 support tickets\nCost: ~$12,500 (direct + indirect)\n\nRoot Cause: Validation middleware broken\nPrevention: Integration tests missing\n\nRecommendations:\n- Add error code validation tests\n- Improve staging coverage\n- Add monitoring for error spikes\n\nLessons Learned:\n- Fast response (8h MTTF)\n- Staging gap allowed escape\n- Need integration test gate\n\nFull postmortem: .aiwg\u002Ftesting\u002Fregression-postmortem-REG-002.md\"\n```\n\n### Quarterly Analysis\n\n```\nUser: \"Quarterly regression analysis\"\n\nSkill generates:\n\"Quarterly Regression Analysis (Q1 2026)\n\nExecutive Summary:\n- 58 total regressions (-35% vs Q4 2025)\n- 3 production escapes (-70% vs Q4)\n- MTTD: 9.2h (↓ from 24h)\n- MTTF: 22h (↓ from 42h)\n\nStrategic Insights:\n- Automation investment paying off (76% faster detection)\n- Integration testing gap remains (40% of regressions)\n- Auth and API modules highest risk\n\nInvestment Recommendations:\n- $50k: Integration test automation\n- $30k: Performance testing platform\n- $20k: Staging environment expansion\n\nFull analysis: .aiwg\u002Ftesting\u002Fregression-analysis-Q1-2026.md\"\n```\n\n## Integration\n\nThis skill uses:\n- `regression-bisect`: Import root cause analysis\n- `regression-baseline`: Import drift data\n- `regression-metrics`: Import statistical trends\n- `project-awareness`: Detect sprints\u002Freleases\n- `traceability-check`: Link to requirements\n\n## Agent Orchestration\n\n```yaml\nagents:\n  synthesis:\n    agent: technical-writer\n    focus: Report generation and clarity\n\n  analysis:\n    agent: metrics-analyst\n    focus: Data correlation and insights\n\n  recommendations:\n    agent: test-architect\n    focus: Prevention strategies\n```\n\n## Configuration\n\n### Report Templates\n\n```yaml\nreport_templates:\n  incident:\n    template: templates\u002Fregression\u002Fincident-report.md\n    sections: [summary, timeline, root_cause, impact, prevention]\n\n  sprint:\n    template: templates\u002Fregression\u002Fsprint-report.md\n    sections: [summary, inventory, metrics, recommendations]\n\n  quarterly:\n    template: templates\u002Fregression\u002Fquarterly-report.md\n    sections: [executive, trends, strategic, investments]\n```\n\n### Data Aggregation\n\n```yaml\naggregation_config:\n  sources:\n    - bisect_reports: .aiwg\u002Ftesting\u002Fregression-bisect-*\u002F\n    - baselines: .aiwg\u002Ftesting\u002Fbaseline-comparisons\u002F\n    - metrics: .aiwg\u002Ftesting\u002Fregression-metrics-dashboard.md\n    - issues: github_issues\n    - incidents: .aiwg\u002Fincidents\u002F\n\n  correlation_rules:\n    - link_bisect_to_issue\n    - map_component_to_owner\n    - calculate_business_impact\n```\n\n## Output Locations\n\n- Reports: `.aiwg\u002Ftesting\u002Fregression-report-{period}.md`\n- Postmortems: `.aiwg\u002Ftesting\u002Fregression-postmortem-{issue}.md`\n- Quarterly: `.aiwg\u002Ftesting\u002Fregression-analysis-Q{n}-{year}.md`\n\n## References\n\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fschemas\u002Ftest\u002Fregression-report-schema.yaml\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fregression\u002Fincident-report.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Ftechnical-writer.md\n- @$AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fagents\u002Fmetrics-analyst.md\n",{"name":5,"namespace":47,"platforms":48,"description":7},"aiwg",[49],"all","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fregression-report",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-12 00:33:10",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add jmagly\u002Faiwg --skill regression-report",{"tool":66,"command":67},"bunx","bunx skills add jmagly\u002Faiwg --skill regression-report",{"tool":69,"command":70},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill regression-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fregression-report\u002FSKILL.md",true,[74,80,84],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"manifest.json","REFERENCE","参考文档",106,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FFrameworks\u002FWPF\u002Fskills\u002Fwpf\u002Fmanifest.json",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fanti-patterns.md",18443,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FFrameworks\u002FWPF\u002Fskills\u002Fwpf\u002Freferences\u002Fanti-patterns.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fpatterns.md",17847,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FFrameworks\u002FWPF\u002Fskills\u002Fwpf\u002Freferences\u002Fpatterns.md",[89,116,139,145,152,166],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":96,"publishedAt":42},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[95],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[97,98,99,100,101,39,102,103,104,105,106,107,108,109,110,111,112,113,114,115],"host","host hardening","hardening","read","re","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":42},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,36,128,100,129,104,130,131,106,132,97,133,108,134,135,111,112,136,137,138],"exposure analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":140,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":42},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[143],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[99,97,98,107,100,115,102,39,110,103,104,105,106,114,108,109,101,111,112,113],{"skillNo":146,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":151,"publishedAt":42},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[149,150],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[36,127,111,129,104,130,106,128,97,133,108,134,135,100,112,132,131,136,137,138],{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":42},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[158],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[160,161,162,163,164,165],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":42},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[172],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,175,134,176,161],"pi","pi local","duplicate"]