ship

Manage Git commit history, tagging, and release artifacts with semantic versioning.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/projectmiluju/factlog --skill ship-projectmiluju
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/projectmiluju/factlog/tree/main/.agents/skills/ship
Command: npx skills add https://github.com/projectmiluju/factlog --skill ship-projectmiluju

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 커밋/태그/릴리즈 관리의 일관성과 추적 가능성을 보장하여 대규모 릴리스에서 변경 내역과 배포를 체계적으로 문서화하는 문제를 해결합니다.

Core Features & Use Cases

  • 엄격한 커밋 메시지 규칙 적용 및 한글 헤더 관리로 기록의 명확성을 확보합니다.
  • 릴리즈 게이트 및 버전 관리 원칙을 적용해 SemVer 준수와 승인 흐름을 자동으로 강제합니다.
  • 릴리즈 산출물(태그, 배포 문서, 변경 로그 기본 형식)의 생성과 문서화를 표준화합니다.
  • Use Case: 팀이 정기 릴리즈 사이클을 운영할 때 변경 이력을 깔끔하게 기록하고 승인된 버전에 대한 배포를 신뢰할 수 있게 합니다.

Quick Start

프로젝트의 릴리즈 프로세스를 시작하려면 새 브랜치를 만들고 PR 템플릿을 적용한 뒤 릴리즈 태그 절차를 따라 진행하세요.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I enforce semantic versioning and code-review gates in Git release workflows?

To enforce semantic versioning and code-review gates in Git release workflows, you need deterministic release practices that automate approval flows. This ensures strict versioning compliance and standardized release documentation across teams.

What is the best way to standardize Git commit messages and release notes for regular release cycles?

Standardizing Git commit messages and release notes requires applying strict commit message rules and standardized changelog formats. This ensures clear change tracking and reliable deployments for regular team release cycles.

How do I manage Git tags and release artifacts to ensure disciplined software delivery?

Managing Git tags and release artifacts involves orchestrating commits, tags, and release documentation systematically. This enforces deterministic release practices and ensures traceable software delivery across teams.

Can I automate release gates and approval flows for SemVer compliance in versioning workflows?

Yes, you can automate release gates and approval flows for SemVer compliance in versioning workflows. Applying release management principles enforces strict versioning rules and automatically gates releases based on approval status.

Does this release management approach work for large-scale software delivery requiring strict versioning?

Yes, this release management approach works for large-scale software delivery requiring strict versioning. It enforces deterministic release practices, including hard gates, semantic versioning, and standardized release notes across teams.