{"slug": "fix-a-pnpm-bug-with-your-coding-agent", "title": "Fix a pnpm bug with your coding agent", "summary": "A developer has published a step-by-step workflow for using a coding agent to contribute a bug fix to the pnpm package manager, covering forking the repo, selecting an unassigned bug via the GitHub CLI, reproducing it with a failing test, making a minimal root-cause fix, and opening a PR that discloses AI assistance. The guide instructs the agent to confirm the chosen issue with the human before proceeding and to comment on the issue if work stops.", "body_md": "|  | I want to contribute a bug fix to pnpm (https://github.com/pnpm/pnpm). | \n|  | 1. Set up | \n|  | - Fork and clone the repo: `gh repo fork pnpm/pnpm --clone`, then cd into it. | \n|  | - Read CONTRIBUTING.md and any AGENTS.md / CLAUDE.md files, and follow them. | \n|  | They explain how to install dependencies, build, run tests, and add changesets. | \n|  | 2. Pick an issue | \n|  | - List open bugs that nobody is working on yet: | \n|  | gh issue list -R pnpm/pnpm --state open --label \"type: bug\" --limit 100 \\ | \n|  | --search \"no:assignee -label:\\\"state: has PR\\\" -label:\\\"state: in progress\\\" -label:\\\"state: blocked\\\" -label:\\\"state: needs design\\\" -linked:pr\" | \n|  | - Choose ONE issue that has clear reproduction steps and a scope you can fix in a | \n|  | single focused PR. Skip issues that need a design decision or depend on a specific OS | \n|  | or registry setup you can't reproduce. | \n|  | - Read the whole thread, and check that there isn't already an open PR for it | \n|  | and that nobody has commented that they are working on it. | \n|  | - Tell me which issue you picked and why before you continue. | \n|  | - Once I confirm, leave a short comment on the issue so others don't start on it too: | \n|  | gh issue comment <number> -R pnpm/pnpm --body \"I'm working on a fix for this.\" | \n|  | 3. Reproduce | \n|  | - Reproduce the bug locally first. If you can't reproduce it, stop and tell me | \n|  | instead of guessing a fix. | \n|  | - Write a failing test that captures the bug. | \n|  | 4. Fix | \n|  | - Make the smallest change that fixes the root cause. Don't refactor unrelated code. | \n|  | - Match the style of the code around it. | \n|  | - Run the tests covering the changed packages, plus lint, and make sure they pass. | \n|  | - Add a changeset if CONTRIBUTING.md asks for one. | \n|  | 5. Open a PR | \n|  | - Commit on a new branch, push to my fork, and open a PR against pnpm/pnpm main | \n|  | with `gh pr create`. | \n|  | - Put \"close #<issue number>\" in the description, explain the root cause and | \n|  | the fix, and say how you tested it. | \n|  | - Mention that the PR was written with the help of an AI agent. | \n|  | - Watch CI and fix any failures. | \n|  | If you stop working on the issue at any point (for example, because you can't reproduce it), | \n|  | comment on it again to say so, so that someone else can pick it up. | \n|  | Apart from the comments above, don't post on the issue or the PR for me without asking first. |", "url": "https://wpnews.pro/news/fix-a-pnpm-bug-with-your-coding-agent", "canonical_source": "https://gist.github.com/zkochan/f5775a9e2e2918775cfdf856bf2a0ad8", "published_at": "2026-09-25 10:54:34+00:00", "updated_at": "2026-09-25 12:01:59.176524+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-tools"], "entities": ["pnpm", "GitHub"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/fix-a-pnpm-bug-with-your-coding-agent", "markdown": "https://wpnews.pro/news/fix-a-pnpm-bug-with-your-coding-agent.md", "text": "https://wpnews.pro/news/fix-a-pnpm-bug-with-your-coding-agent.txt", "jsonld": "https://wpnews.pro/news/fix-a-pnpm-bug-with-your-coding-agent.jsonld"}}