pr-make-accountable

Interviews PR authors and co-authors What, Why, and Changes pull request descriptions.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill pr-make-accountable-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-make-accountable
Source: https://github.com/nseng-ai/ns/tree/main/skills/public/prs/pr-make-accountable
Command: npx skills add https://github.com/nseng-ai/ns --skill pr-make-accountable-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auto-generated PR descriptions are usually walls of text that summarize the diff without communicating intent, rationale, tradeoffs, or rejected alternatives. This Skill interviews the PR author to surface the context the code cannot supply, then co-authors an accurate, human-accountable PR description. ## Core Features & Use Cases - Structured author interview: Inspects the PR with git and gh, builds an inventory of design decisions and gaps, then asks one targeted question at a time until author and agent share an accurate understanding. - Co-authored PR body: Writes a What / Why / Changes description with an optional opt-in Requested reviewer focus section, representative examples for user-facing changes, and a provenance footer naming the model and harness. - Consumability report: Verdicts on size, title honesty, narrative, and reviewer focus, plus open topics and unencoded durable policy discovered during the interview. - Use Case: After pushing a feature branch, run the skill from the checked-out branch; it challenges unclear reasoning, lets you amend the PR mid-interview, and publishes an honest description reviewers can act on. ## Quick Start Run /pr-make-accountable from the checked-out branch of an existing PR in a repo with git and an authenticated gh session, optionally adding a sentence of rationale after the invocation.

Frequently Asked Questions about pr-make-accountable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a better pull request description with an AI agent?

Run pr-make-accountable from the checked-out branch of an existing PR. The agent inspects the diff, interviews you about intent and tradeoffs, then co-authors a What / Why / Changes body and writes it to the PR with gh pr edit.

How does the PR author interview process work?

The agent builds an inventory from the net diff, then asks one open-ended question per turn about material gaps such as rationale, rejected alternatives, and limitations. You can amend the PR mid-interview, and drafting begins only when every material topic is shared or openly stated.

What tools does pr-make-accountable require?

It requires only git and an authenticated GitHub CLI (gh) session. It uses gh for PR metadata and body updates and local git for diff inspection, with no dependency on the ns repository or other tooling.

Can I use this skill on a branch without an existing PR?

No. The skill targets the checked-out branch's existing PR and stops if none exists, asking you to create or push one first using your repository's normal Git and PR workflow.

When does the PR description include usage examples?

Examples appear only when the final net diff changes behavior observable by an intended user, such as CLI output, API responses, or UI behavior. Implementation-only changes omit examples entirely, and every example must be supported by implementation evidence.

Does the agent decide the final PR description?

No. The agent writes a live draft, but the author must read every claim and edit anything false or unlike their voice. The author's wording wins, and a provenance footer discloses that the description was co-authored with the model.