pr-with-docs — community pr-with-docs, ai-workflow-cursor-config, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Git-based AI Agents needing streamlined pull request creation and documentation updates. 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

pmagnomuller pmagnomuller
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reviewed Landing Page Review Score: 9/11

Killer-Skills keeps this page indexable because it adds recommendation, limitations, and review signals beyond the upstream repository text.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review Locale and body language aligned
Review Score
9/11
Quality Score
50
Canonical Locale
en
Detected Body Locale
en

Ideal for Git-based AI Agents needing streamlined pull request creation and documentation updates. 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

Core Value

Empowers agents to automate Git workflows, updating AGENTS.md and running change analysis for features, bug fixes, and refactors, while supporting .cursor/rules updates and creating pull requests.

Ideal Agent Persona

Ideal for Git-based AI Agents needing streamlined pull request creation and documentation updates.

↓ Capabilities Granted for pr-with-docs

Automating pull request creation with updated documentation
Analyzing changes for scope identification and AGENTS.md updates
Streamlining Git workflows for AI agent development

! Prerequisites & Limits

  • Requires Git workflow integration
  • Limited to updating AGENTS.md and .cursor/rules files

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is pr-with-docs?

Ideal for Git-based AI Agents needing streamlined pull request creation and documentation updates. 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

How do I install pr-with-docs?

Run the command: npx killer-skills add pmagnomuller/ai-workflow-cursor-config/pr-with-docs. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for pr-with-docs?

Key use cases include: Automating pull request creation with updated documentation, Analyzing changes for scope identification and AGENTS.md updates, Streamlining Git workflows for AI agent development.

Which IDEs are compatible with pr-with-docs?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for pr-with-docs?

Requires Git workflow integration. Limited to updating AGENTS.md and .cursor/rules files.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add pmagnomuller/ai-workflow-cursor-config/pr-with-docs. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use pr-with-docs immediately in the current project.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

pr-with-docs

Install pr-with-docs, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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.
  • If on main/master, create a feature branch: <type>/<brief-description> (e.g. feature/add-instagram-scraping, fix/auth-redirect-loop, docs/update-schema-info). Types: feature, fix, docs, refactor, chore.
  • If already on a feature branch, use it.

Stash

  • Check uncommitted changes: git status.
  • If there are uncommitted changes: git stash push -m "Auto-stash before PR creation".
  • Restore stash after operations if one was created.

Commit

  • Stage docs first: git add AGENTS.md (and any .cursor/rules/*.mdc if changed).
  • Commit docs: git commit -m "docs: update AGENTS.md with [specific changes]".
  • Stage rest: git add .
  • Commit code with conventional commits: <type>(<scope>): <description> (e.g. feat(auth): add Google OAuth support).

Publish

  • Push: git push -u origin <branch-name>.
  • Handle push conflicts or errors.

4. Pull Request

  • Use GitHub CLI: gh pr create (or host-appropriate CLI).
  • PR description should include:
    • Summary: 2–3 sentence overview.
    • Changes Made: Bulleted list.
    • Documentation Updates: AGENTS.md (and rules) sections updated.
    • Testing: How changes were tested (if applicable).
    • Breaking Changes: Any breaking changes or migration steps.
    • Related Issues: Links if mentioned.
  • Title in conventional commits style; add labels (feature, bugfix, documentation, etc.) if possible.

When to Update AGENTS.md

ChangeUpdate
New files in apps/api/ (routes, models, services)Repo Layout, Conventions, Key Files
New files in apps/api/migrations/Repo Layout, Database/Migrations
New env vars in codeConventions / README env section
New packagesRepo Layout / Tech stack
New dev commandsWhere to Run Commands
Auth logic changesConventions, Auth
New component/API patternsConventions, Key Files
New third-party integrationsConventions or new subsection

When NOT to Update AGENTS.md

  • Minor bug fixes that do not change architecture.
  • Internal refactors that do not affect usage patterns.
  • Styling tweaks following existing patterns.
  • Test file additions (unless they introduce new testing patterns).

Quality Before PR

  1. AGENTS.md is valid Markdown with no syntax errors.
  2. Code examples in AGENTS.md use correct syntax.
  3. All Git operations completed successfully.
  4. Commits follow conventional commits format.
  5. PR description is accurate and complete.

Error Handling

  • If Git fails: clear error message and suggested fix.
  • If AGENTS.md updates are unclear: ask the user.
  • If PR creation fails: give the user the PR description for manual creation.
  • Always clean up: restore stash, return to original branch if needed.

Communication

  • Give a short status at each phase.
  • Say which AGENTS.md (and rules) sections you are updating and why.
  • Show commit messages before committing and PR description before creating.
  • Ask for confirmation if changes are ambiguous or potentially breaking.
  • Proactively mention related docs that could be updated.

Output Phases

  1. Analysis: "Analyzing changes in current branch..."
  2. Documentation: "Updating AGENTS.md sections: [list]..."
  3. Git: "Creating branch / committing changes..."
  4. PR: "Creating pull request..."
  5. Summary: PR URL and brief summary of actions.

Goal: merge-ready PRs with documentation in sync with the codebase.

Related Skills

Looking for an alternative to pr-with-docs or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer