Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "shiplog" skill in my project. Repository: https://github.com/devallibus/shiplog Please read the repo to find the SKILL.md file(s), then: 1. Download them into the correct skills directory (.claude/skills/ or .cursor/skills/) 2. Include any companion files referenced by the skill 3. Confirm what was installed and where
Description
Git-as-knowledge-graph workflow for traceability. Use when planning work, brainstorming designs, creating/managing issues and PRs, tracking architectural decisions, or resuming prior sessions. Slash command /shiplog.
Shiplog
The captain's log for your codebase. Every decision, discovery, and change logged as you ship code. Use GitHub as a complete knowledge graph where every brainstorm, commit, review, and decision is traceable. This skill orchestrates existing skills and references; it defines when and how to invoke them and what documentation protocol to follow.
Core Principle
Nothing gets lost. Every brainstorm becomes an issue. Every issue drives a branch. Every branch produces a PR. Every PR is a timeline of the entire journey. Git becomes the uber-memory. ---
Mode Selection
On first activation per project, ask the user which mode to use: • Full Mode (default): Knowledge goes directly into issues and PRs. For personal projects, OSS, and teams that embrace documentation. • Quiet Mode: Knowledge lives in a stacked knowledge branch (<branch>--log) with its own PR targeting the feature branch. For work environments where issues and PRs must stay clean. Remember the choice via ork:remember or note it in project instructions. ---
When This Skill Activates
User-invocable: /shiplog, /shiplog models, /shiplog <phase> /shiplog models: Re-runs the routing setup prompt. See references/model-routing.md. Auto-activate when ANY of these occur: • User says "let's plan", "let's brainstorm", or "let's design" • User explicitly requests traceability or knowledge-graph tracking • Creating a new issue or PR with intent to document decisions • Mid-work discovery requiring a new issue or stacked PR • User asks "where did we decide X?" or "what's the status of Y?" • Resuming work on an existing issue or PR • Applying review feedback, fixing review findings, or addressing request-changes dispositions • User references an issue or PR by number Do NOT auto-activate for: • Generic coding requests that do not need traceability • Simple bug fixes or refactors that do not need durable workflow history • Work where a more specific skill is the better fit ---
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster