ship-it
Ship Changes Through Pull Requests and CI
Finishing a change requires careful verification, commits, pull-request setup, and CI follow-through. This skill manages that workflow until every check passes.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ship-it" from https://skillstore.io/skills/jssblck-ship-it.md and its manifest at https://skillstore.io/api/skills/jssblck-ship-it/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "ship-it". Ship the completed cache fix and reference issue 142.
Expected outcome:
Opened a ready pull request for issue 142. Unit tests, linting, formatting, and the full CI matrix passed.
Using "ship-it". Get the current pull request green after the integration test failed.
Expected outcome:
- Reviewed the complete failed-job log and corrected the stale fixture.
- Reran the relevant local tests and pushed one focused fix commit.
- All pull-request checks now pass.
Using "ship-it". Commit these documentation updates and open a pull request.
Expected outcome:
Created a focused documentation commit and opened a ready pull request with the validation results. All required checks passed.
Security Audit
SafeAll 19 static findings are false positives caused by Markdown code formatting, explicit GitHub CLI examples, or safely quoted heredoc command substitutions. No prompt injection, credential access, data exfiltration, or arbitrary command construction was found.
Risk Factors
⚙️ External commands (18)
🔑 Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/jssblck-ship-it/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/jssblck-ship-it?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/jssblck-ship-it?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jssblck-ship-it/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/jssblck-ship-it.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
jssblck. (2026). ship-it security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jssblck-ship-it/audits/1BibTeX citation
@techreport{jssblck-jssblck-ship-it-2026,
author = {jssblck},
title = {ship-it security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/jssblck-ship-it/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ship-it security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "jssblck"
date-released: "2026-08-23"
url: "https://skillstore.io/skills/jssblck-ship-it/audits/1"
identifiers:
- type: other
value: "skillstore:jssblck-ship-it:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Finish a feature branch
Verify completed work, create logical commits, open a ready pull request, and monitor CI.
Resolve pull-request failures
Inspect failed CI logs, correct the implementation, rerun local gates, and push a focused fix.
Standardize delivery evidence
Produce consistent commit messages, pull-request context, testing records, and a final green-status report.
Try These Prompts
Use $ship-it to verify the current changes, commit them, open a ready pull request, and wait for all CI checks.
Use $ship-it for this branch. Run the repository checks that cover the changed modules, then create the pull request and resolve CI failures.
Use $ship-it to reuse the open pull request for this branch. Refresh its details, mark it ready, and drive every check to green.
Use $ship-it to inspect the full diff and split related changes into logical commits. Link the issue, document exact tests, and resolve the complete CI matrix.
Best Practices
- Review the complete diff and preserve unrelated user changes before invoking the workflow.
- Keep repository documentation and CI configuration accurate so local verification matches required checks.
- Confirm GitHub authentication and branch protections before starting a workflow that may require approval.
Avoid
- Do not invoke the skill on the default branch when the repository requires feature branches.
- Do not treat skipped integration tests as successful coverage without checking required services.
- Do not stop after one passing job when other matrix jobs or required checks remain.
Frequently Asked Questions
Does this skill push changes automatically?
Can it work with an existing pull request?
How does it choose local checks?
What happens when CI fails?
Does it require GitHub CLI access?
When does the workflow pause?
Developer Details
Author
jssblckLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/jssblck/agents/tree/4658295e88faed205cc134edf987f7ea4e0c8ea4/skills/ship-itRef
f1f20eafa082e205df578f5570f3f4383ce3374a
Maintenance freshness
8/23/2026
Usage
0 downloads · 0 views
File structure