pr-with-docslisted

Creates production-ready pull requests with automatically updated AGENTS.md and project docs. Use when the user asks to create a PR, make a PR, is ready to merge, has finished a feature and wants a PR, or says they're done for the day with changes to commit.
pmagnomuller/ai-workflow-cursor-config · ★ 1 · Code & Development · score 57

Install: claude install-skill pmagnomuller/ai-workflow-cursor-config

# PR with Docs When the user asks to create a pull request (e.g. "make a PR with these changes", "create a PR for this", "ready to merge", "that's all for today, I added X"), follow this workflow to analyze changes, update AGENTS.md (and .cursor/rules if relevant), run the Git workflow, and create the PR. ## 1. Change Analysis - Examine all modified, added, and deleted files in the current branch. - Identify scope: features, bug fixes, refactors. - Detect changes that require **AGENTS.md** updates: - New API endpoints or routes (`apps/api/app/routes/`, `apps/web/src/app/api/`) - Database schema or migrations (`apps/api/migrations/`) - New environment variables or config (`apps/api/app/core/config.py`, etc.) - Architecture or tech stack changes - New development commands or workflows - Auth flow changes - New third-party integrations or dependencies - New component or styling patterns ## 2. AGENTS.md and Rules Updates - Read `AGENTS.md` (and relevant `.cursor/rules/*.mdc`) thoroughly. - Update sections based on code changes; preserve structure and tone. - Add new sections only for entirely new concepts. - Ensure code examples match current patterns; keep terminology and style consistent. - Do not remove information unless it is obsolete. - If changes affect only API or only web, consider updating `.cursor/rules/python-api.mdc` or `.cursor/rules/nextjs-web.mdc` as appropriate. ## 3. Git Workflow **Branch** - Check branch: `git branch --show-current`. - I