Pre Ship Review
CheckedAutomatically flags potential shipping errors, missing documentation, or compliance issues before product dispatch.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add terrylica/cc-skills --skill pre-ship-review -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
terrylica
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned terrylica/cc-skills at 3a1dc29965.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3a1dc29965
- Scanned
- 6 files, 1,172 lines
About this skill
What it does
The Pre Ship Review skill performs a structured quality review of code before shipping, whether that's through pull requests, releases, or milestones. It focuses on identifying failures at integration boundaries – areas where contracts, examples, constants, and tests must align. The core principle is that AI-generated code often excels in isolated components but struggles with interactions between them; this skill systematically checks those interaction points to prevent shipping errors, missing documentation, or compliance issues.
When to use it
This skill is valuable in the following situations:
- Pull requests introducing multiple new modules that need to work together.
- Releases combining code from different contributors or branches.
- Milestones where quality gates must be passed before proceeding.
- Any checkpoint involving code with examples, constants across files, or interface extensions requiring validation.
Key capabilities
- Automated checks using external tools like Pyright, Vulture, and Semgrep.
- Orchestration of other AI skills (cc-skills) for deeper analysis, including code auditing and dead code detection.
- Verification of function parameter usage, configuration mappings, and domain constant correctness.
- Test quality assessment to ensure tests accurately reflect behavior.
- Identification of architectural boundary violations and implicit dependencies.
- Provides a compiled report with findings, severity levels, and suggested fixes.
- Offers three templates: New Feature Ship, Bug Fix Ship, and Refactoring Ship, each tailored for specific scenarios.
Example prompts
Here are some example prompts you might use with an AI agent equipped with this skill:
- "Run a Pre-Ship Review on this pull request."
- "Perform a 'New Feature Ship' review of the code changes in milestone X."
- "Execute the 'Bug Fix Ship' template for these modified files."
Tips & gotchas
- Template Selection is Mandatory: Always select and load the appropriate template (New Feature, Bug Fix, or Refactoring) before starting a review.
- Self-Evolving Nature: The skill improves with use; update it immediately when encountering issues or needing workarounds.
- Not for Minor Changes: This skill isn't necessary for single-file cosmetic changes, documentation updates, or dependency bumps.