forge-ship

Finalize Forge development cycles by generating summaries, running quality checks, and creating pull requests.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jupes/agent-forge-harness --skill forge-ship-jupes
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: forge-ship
Source: https://github.com/jupes/agent-forge-harness/tree/main/.claude/skills/forge-ship
Command: npx skills add https://github.com/jupes/agent-forge-harness --skill forge-ship-jupes

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the finalization process of development cycles within the Forge pipeline, ensuring a cohesive summary, quality checks, and PR creation.

Core Features & Use Cases

  • Pipeline Finalization: Summarizes the entire workload, closes Beads issues, and facilitates a step-by-step verification.
  • Quality Assurance: Runs quality gates, including typecheck, lint, and tests, to ensure code integrity before pushing.
  • PR Creation: Automates the creation of pull requests with detailed reports and walkthroughs for code review.
  • Use Case: After a successful implementation phase, use this Skill to finalize the work, generate a comprehensive report, and open a PR with the necessary information.

Quick Start

Run the /forge-ship <slug> command to finalize the development cycle and open a PR for the <slug> feature.

Frequently Asked Questions about forge-ship

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

FAQPage Schema
How do I automate code review and PR creation at the end of a development cycle?β–Ό

Automating PR creation and code review at the end of a development cycle involves running quality assurance checks, generating summaries, and opening pull requests. This finalization process ensures code integrity by validating typecheck, lint, and tests before submitting work for review.

What is a development pipeline finalization process?β–Ό

A development pipeline finalization process is the step-by-step verification of workload completion, closing issue tracking tickets, and executing quality gates. It ensures implemented features pass typecheck, lint, and tests before generating a comprehensive report for code submission.

How do I run quality assurance checks before opening a pull request?β–Ό

Running quality assurance checks before opening a pull request is done by executing automated quality gates for typecheck, lint, and tests. This ensures code integrity and verifies the implementation phase is successful before creating the PR with detailed reports.

Do I need a specific issue tracking system to automate project finalization?β–Ό

Yes, automating project finalization requires a well-defined Forge state and Beads issue tracking. The finalization process relies on this specific environment to summarize the workload, close associated Beads issues, and facilitate proper step-by-step verification.

What is the best way to generate a summary for a completed development cycle?β–Ό

The best way to generate a summary for a completed development cycle is through pipeline finalization automation that summarizes the entire workload. This approach closes tracked issues and produces detailed reports with walkthroughs directly attached to the newly created pull request.