Ship Pr

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 118e61cf1c61 · 16 Oct 2026Report an issue or request a re-scan

• Publisherpedronauck GitHub userOwner of the repository this skill is read from
• Source folderpedronauck/skills/skills/mine/ship-prThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict118e61cf1c61A new audit runs when the source changes
• Repository statusNot archivedLast push 31 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Deliver implementation-complete work with impact/docs checks, release notes, commits, and a PR; optionally watch CodeRabbit. Excludes unfinished checkpoints, draft-only PRs, merged-PR amendments, and release publication.

---
name: ship-pr
description: "Deliver implementation-complete work with impact/docs checks, release notes, commits, and a PR; optionally watch CodeRabbit. Excludes unfinished checkpoints, draft-only PRs, merged-PR amendments, and release publication."
disable-model-invocation: true
metadata:
  author: Pedro Nauck
  github: https://github.com/pedronauck
  repository: https://github.com/pedronauck/skills
---
# Ship a PR

Finish the requested delivery scope using the repository's conventions. Reuse the implementation's impact analysis, current checks, and QA evidence. Do not turn preparing a PR into a release or automated review campaign unless requested or required by the project.

1. Inspect branch/base, staged and unstaged changes, relevant instructions, PR template, and current verification. Already-committed work is valid input. Keep unrelated changes out of staging.
2. Trace changed public behavior to its affected documentation, examples, config, and release notes. A focused diff can be inspected locally; bounded independent agents help only for distinct large areas.
3. Update the affected artifacts. Follow repository release-note policy; a binary on PATH does not establish repository adoption. Group related changes instead of creating a note for every bullet.
4. Write a PR description around the resulting behavior, material risks, and actual validation. Use the repository template; omit empty optional sections. Include existing QA artifacts only when they explain the change.
5. Before committing, run required scoped gates or reuse valid evidence as project policy allows. Stage owned paths explicitly and inspect the staged diff. Follow commitlint and hook requirements; no invented model attribution, history rewrite, or hook bypass.
6. When commit/push/PR creation is within the user's request, publish the feature branch and create or update its PR with `gh` using a body file. Respect requested draft status. Follow required CI to the current head; triage failures as they appear.
7. Start an external review watcher only when requested or already part of the authorized delivery workflow. Confirm the installed command and configured provider. Automatic remediation, commits, pushes, and unbounded polling are separate scope choices, not tool-detection defaults.

## References

Load the phase that needs detail: `references/explore-impact.md`, `references/release-notes.md`, `references/pr-description.md`, `references/qa-artifacts.md`, `references/commit-conventions.md`, or `references/coderabbit-watch.md`.

The read-only detector is `bash <ship-pr-dir>/scripts/detect-tooling.sh`, resolved relative to this skill. Its PATH results describe availability, not authorization or project configuration. Missing optional integrations do not block the normal PR flow. Sync Skeeper only for configured repositories with affected spec artifacts.

Excerpt, first 2,878 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/pedronauck/skills
git -C skills checkout 118e61cf1c61

Works in

1. 2026-10-16
   ✓SAFE B 89 / 100

   first audit · source 118e61cf1c61

Questions about Ship Pr

• github.com/pedronauck/skills/tree/main/skills/mine/ship-pr — the audited source at commit 118e61cf1c61 and every finding aboveObserved · 16 Oct 2026

Spotted something wrong? Report a correction · Methodology