skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
akshay-diwadkar/first-four-hours81 installs

pr

Write a grounded, reviewer-oriented pull request description for the current branch and open or update its PR only after explicit user confirmation. Use when a finished branch needs a PR or a refreshed description; never merges.

How do I install this agent skill?

npx skills add https://github.com/akshay-diwadkar/first-four-hours --skill pr
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubwarn

    The skill facilitates pull request management and verification by allowing the agent to execute arbitrary shell commands to record test runs. While this capability is central to the skill's purpose, it creates a risk of command execution if the agent is influenced by malicious instructions in untrusted external data sources such as GitHub issues or project documentation.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

PR

Write what a reviewer needs and the diff cannot show, check it mechanically, and open the PR only after the user confirms the exact text. Never merge, approve, or edit the branch's code.

Ground

  1. Fix the base ref (for example origin/main) and read the whole git diff <base>...HEAD. If gh pr view <branch> --json state shows OPEN, read Update first.
  2. Find the authority: the linked issue (gh issue view <n>) or a sealed .first-four-hours/blueprints/*/blueprint.md. Link or quote its intent, decisions, and acceptance criteria; never re-author them as a second source of truth. With neither, say so and take intent from the user.
  3. From a clean worktree at the commit you will push, run each verification you will claim through record, one arg per argv element:
python <skill-root>/scripts/cli.py --repo-root <repo> --input runs=<runs.jsonl> \
  --input arg=<argv0> --input arg=<argv1> --format json record

Its result gives the real exit_code and the command string to cite.

Draft

Read Description guide, then write the draft outside the repository, next to <runs.jsonl>.

Check

python <skill-root>/scripts/cli.py --repo-root <repo> --input draft=<draft.md> \
  --input runs=<runs.jsonl> --input base=<base> --format json check

Repair each diagnostic in the draft, or record the missing run, and rerun until it passes. The script checks only grounding, recorded runs, and Mermaid shape, never prose quality; the content and every diagram are your judgment.

Confirm and open

Show the user the title and the complete checked draft, and ask whether to open the PR, and to push the branch first when its upstream is missing or behind. Only an explicit yes authorizes it; silence or an earlier approval does not. After a yes, push if needed, then:

python <skill-root>/scripts/cli.py --repo-root <repo> --input draft=<draft.md> \
  --input runs=<runs.jsonl> --input base=<base> --input title=<title> \
  --input confirm=<body_sha256 from check> --format json publish

confirm binds the exact text the user saw; after any edit, check, show, and ask again. Report the PR URL. End with one optional next step fitting this outcome: a fenced, self-contained prompt naming any repository, issue, PR, or artifact it needs, or say none is needed. Only a "yes" starts it, via any skill it names, but the user runs a charter, diagnose, or ticket step as its /<skill> command. Never merge the PR.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/akshay-diwadkar/first-four-hours/pr">View pr on skillZs</a>