القائمة
Use when the implementation of a feature or bugfix is complete and you need to generate a professional, conventional pull request description summarizing the changes against the main branch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
PostHog integration for Next.js App Router applications
Use when a feature branch is complete and ready for PR — runs a full diff-based review of the current branch against main, reads every changed file, validates against project rules, and produces a concrete action plan. Do NOT use on main branch.
Identifies and executes the next pending POC task. Fast context pickup from docs/poc/context.json — no build/lint at start. Use for starting the next task, resuming in-progress work, or targeting a specific task by ID.
Use when the Antes da Tela POC needs a new task direction or clearer scope before handing work off to /create-poc-task in the documented AI workflow.
Analyzes current POC task state, creates a standardized new task file, and updates docs/poc/context.json and docs/poc/tasks/summary.md. Use when adding a new task to the Antes da Tela POC backlog.
Unified Figma implementation + refinement workflow that translates Figma designs into production-ready code, reconciles design tokens, and performs regression-safe metadata updates. Use live MCP data with canonical metadata under `docs/design-system/`.
| name | create-pr |
| description | Use when the implementation of a feature or bugfix is complete and you need to generate a professional, conventional pull request description summarizing the changes against the main branch. |
Analyzes current branch changes (staged and unstaged) relative to main and generates a structured, professional PR description in English following Conventional Commits and project best practices.
Core principle: Summarize the "What" and "Why" while providing a clear checklist for reviewers.
Identify the current branch and compare it to main (or master).
git branch --show-current
git diff --name-status main...HEAD
git diff main...HEAD
Include all staged and unstaged changes in your mental model of the current state.
Format the output in clear, professional English:
feat: add user profile page).Title: <conventional-title>
<detailed description>
Checklist:
- [ ] Tests
- [ ] Documentation
- [ ] Database migration (if applicable)
- [ ] Ready for review
| Mistake | Fix |
|---|---|
| Incomplete diff | Include both staged and unstaged changes in analysis. |
| Vague title | Use imperative mood and type (feat, fix, refactor, etc.). |
| Missing breaking changes | Clearly highlight any backward-incompatible changes. |
| Using non-English | Always generate the PR description in English. |
Called after: code-review and verification-before-completion.
Called before: finishing-a-development-branch.