feat(skills): add shared task workflows
This commit is contained in:
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: api-review
|
||||
description: Review API changes for compatibility and contract clarity.
|
||||
---
|
||||
|
||||
# API Review
|
||||
|
||||
Inspect request and response contracts, validation, errors, authorization, compatibility, and documentation.
|
||||
|
||||
Return concrete findings and affected consumers. Keep detailed API standards for future customization.
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: business-review
|
||||
description: Review a change against stated business intent and workflows.
|
||||
---
|
||||
|
||||
# Business Review
|
||||
|
||||
Check actors, workflows, domain concepts, invariants, edge cases, and acceptance criteria.
|
||||
|
||||
Separate stated requirements, evidence, and assumptions. Do not invent business requirements.
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
name: code-review
|
||||
description: Review code for correctness, maintainability, and regressions.
|
||||
---
|
||||
|
||||
# Code Review
|
||||
|
||||
Inspect the change independently and report concrete findings with severity and evidence.
|
||||
|
||||
Check behavior, regressions, maintainability, unnecessary complexity, and verification.
|
||||
|
||||
Do not modify code unless explicitly asked.
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: efcore-review
|
||||
description: Review Entity Framework Core changes for correctness and data access risks.
|
||||
---
|
||||
|
||||
# EF Core Review
|
||||
|
||||
Inspect queries, relationships, tracking, migrations, transactions, and performance-sensitive access.
|
||||
|
||||
Return concrete findings and relevant verification. Keep detailed EF Core standards for future customization.
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: performance-review
|
||||
description: Review changes for meaningful performance risks.
|
||||
---
|
||||
|
||||
# Performance Review
|
||||
|
||||
Identify measurable or plausible bottlenecks in the changed paths.
|
||||
|
||||
Return evidence, expected impact, and proportionate recommendations. Avoid speculative optimization.
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: security-review
|
||||
description: Review changes for concrete security weaknesses.
|
||||
---
|
||||
|
||||
# Security Review
|
||||
|
||||
Inspect trust boundaries, input handling, authorization, secrets, permissions, and sensitive data.
|
||||
|
||||
Return evidence, impact, and actionable findings. Do not invent vulnerabilities without evidence.
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: ui-ux-review
|
||||
description: Review user interface changes for usability and consistency.
|
||||
---
|
||||
|
||||
# UI UX Review
|
||||
|
||||
Inspect states, feedback, accessibility basics, consistency, and error handling.
|
||||
|
||||
Return concrete findings with affected user flows. Keep detailed design standards for future customization.
|
||||
@@ -0,0 +1,10 @@
|
||||
---
|
||||
name: wpf-review
|
||||
description: Review WPF changes for correctness and maintainability.
|
||||
---
|
||||
|
||||
# WPF Review
|
||||
|
||||
Inspect the changed WPF views, bindings, resources, commands, and lifecycle behavior.
|
||||
|
||||
Return concrete findings and relevant verification. Keep detailed WPF standards for future customization.
|
||||
Reference in New Issue
Block a user