القائمة
Generates a well-structured PR description from the current changes. Use after implementing changes and before creating a pull request. Analyzes the diff and creates a comprehensive description.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full WCAG 2.2 AA accessibility audit procedure. Goes beyond the reference checklist with step-by-step testing methodology, tooling, and remediation guidance.
Design a RESTful API from requirements. Use when creating a new API, adding endpoints, or restructuring an existing API. Produces endpoint specifications, schemas, and implementation guidance.
Assess system architecture, identify risks and bottlenecks, document decisions with ADRs. Covers modular monolith, microservices, event-driven, and serverless patterns.
Shift Left quality gates, feature flag pipelines, and deployment automation. Use when setting up or modifying build and deploy pipelines, or when establishing quality gates for a project.
Perform a thorough code review with structured feedback. Use when reviewing pull requests, code submissions, or when you want a quality check on your code. Covers correctness, security, performance, readability, and maintainability.
Reduce complexity while preserving exact behavior. Use when code works but is harder to read or maintain than it should be. Applies Chesterton's Fence — understand the code before simplifying it.
| name | pr-description |
| description | Generates a well-structured PR description from the current changes. Use after implementing changes and before creating a pull request. Analyzes the diff and creates a comprehensive description. |
Analyze the changes: Review all modified/created/deleted files to understand:
Generate the PR description using this template:
## What
[Brief description of what this PR does — 1-2 sentences]
Closes #[issue-number]
## Why
[Why this change is needed — reference the issue context]
## How
[Technical approach taken — key decisions and tradeoffs]
### Changes
- **[file/module]**: [what changed and why]
- **[file/module]**: [what changed and why]
## Testing
- [ ] Existing tests pass
- [ ] New tests added for [describe]
- [ ] Manual testing done for [if applicable]
## Screenshots
[If UI changes, include before/after]
## Notes for Reviewers
[Any context that helps review: areas of uncertainty, alternative approaches considered, things to look out for]