D
devallibus/shiplog
SUPERCHARGE AI-assisted development by using Git
View on GitHub ↗Link checked 2026-11-14 · HTTP 200 · opens the vendor's own site
Official descriptionSUPERCHARGE AI-assisted development by using Git. Cross-model review gates, evidence-linked closure, verification profiles, model-tier routing, artifact envelopes, and provenance signing — all from a single skill for Claude Code, Codex, and Cursor.
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"devallibus-shiplog": {
"command": "npx",
"args": ["skills", "add", "devallibus/shiplog"]
}
}
}Parsed from the README we fetched on 2026-11-13; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"devallibus-shiplog": {
"command": "npx",
"args": ["skills", "add", "devallibus/shiplog"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio devallibus-shiplog -- npx skills add devallibus/shiplog
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 56 ★ · devallibus/shiplog · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-11-14 · last seen 2026-11-14 · seen 1× · listed by 1 sources
- Score
- score 103 · 56 ★ · 1 sources · repo
- Install
npx skills add devallibus/shiplog
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx skills add devallibus/shiplog. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
devallibus/shiplog；first catalogued 2026-11-14；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# shiplog
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
shiplog keeps a project's discussion, decisions, and work context in GitHub issues and PRs, so you can recall what you said and the next agent session can pick up the work. It is a skill (plain markdown instructions) for Claude Code, Codex, and Cursor, for people who plan and build with coding agents and want that history to outlive the chat window.
## Install
bash
npx skills add devallibus/shiplog --skill shiplog
The skill directory is self-contained: a skill-only install has every procedure it needs. Add --agent claude-code, --agent codex, or --agent cursor to target one agent; run npx skills update to refresh.
As a Claude Code plugin, which also adds the slash commands /shiplog:plan, /shiplog:start, /shiplog:capture, /shiplog:commit, /shiplog:pr, /shiplog:lookup, /shiplog:hunt, /shiplog:resume, /shiplog:review, and /shiplog:models:
bash
/plugin marketplace add devallibus/shiplog
/plugin install shiplog@shiplog
From a local checkout: claude --plugin-dir .. The slash commands are short entry points to the same procedures in skills/shiplog/; plain requests ("save this idea", "resume #42") work without them.
## What you get: three records
1. The original discussion, verbatim. Your messages are copied in order, unedited, with who said them and who recorded them. Rejected ideas and doubts stay in. Corrections are added as new entries; earlier wording is never rewritten. A source entry, posted as an issue comment:
markdown
Source: Codex session, messages 2-3. Recorded by: assistant.
Coverage: available messages only.
### Message 2
Speaker: user
text
but i wouldn't want to lose the things i said as a human, you know
2. One current summary in the tracking issue body: goal, current decisions (each linked to its source entry), tasks, checks, and next action. It is edited when facts change, not appended to.
markdown
## Goal
A small core that preserves human discussion and compact retrieval.
## Current decisions
Routing stays as an option, off by default (source).
## Tasks
[x] T1: Capture discussion verbatim
[ ] T2: Make resume read the summary first
## Next action
Implement T2.
3. A small retrieval index. New records start with the short envelope shown above. The helper skills/shiplog/scripts/shiplog-read.sh returns those compact fields first, and full text only when the question needs it:
bash
shiplog-read.sh index # one line per open issue and PR: kind, tasks, labels, title, summary
shiplog-read.sh show 42 # #42's envelope, computed tasks, open tasks, one line per enveloped comment
shiplog-read.sh source 42 # exact text of the kind: source comments on #42
shiplog-read.sh search "auth" # matching issues, PRs, and local commits, one line each
Add -R OWNER/REPO before the command to read another repository. Task counts are computed from the checkboxes; no copies of derived state are stored. Only records from accounts GitHub marks as OWNER, MEMBER, or COLLABORATOR count as project records; envelopes from anyone else are shown as untrusted, with author and link only. Byte and API-call measurements for the helper are in tests/reader/MEASUREMENTS.md.
## A day with it
1. "Save this idea": the discussion becomes an issue with a source entry. No branch needed.
## Install
bash
npx skills add devallibus/shiplog --skill shiplog
The skill directory is self-contained: a skill-only install has every procedure it needs. Add --agent claude-code, --agent codex, or --agent cursor to target one agent; run npx skills update to refresh.
As a Claude Code plugin, which also adds the slash commands /shiplog:plan, /shiplog:start, /shiplog:capture, /shiplog:commit, /shiplog:pr, /shiplog:lookup, /shiplog:hunt, /shiplog:resume, /shiplog:review, and /shiplog:models:
bash
/plugin marketplace add devallibus/shiplog
/plugin install shiplog@shiplog
From a local checkout: claude --plugin-dir .. The slash commands are short entry points to the same procedures in skills/shiplog/; plain requests ("save this idea", "resume #42") work without them.
## What you get: three records
1. The original discussion, verbatim. Your messages are copied in order, unedited, with who said them and who recorded them. Rejected ideas and doubts stay in. Corrections are added as new entries; earlier wording is never rewritten. A source entry, posted as an issue comment:
markdown
Source: Codex session, messages 2-3. Recorded by: assistant.
Coverage: available messages only.
### Message 2
Speaker: user
text
but i wouldn't want to lose the things i said as a human, you know
2. One current summary in the tracking issue body: goal, current decisions (each linked to its source entry), tasks, checks, and next action. It is edited when facts change, not appended to.
markdown
## Goal
A small core that preserves human discussion and compact retrieval.
## Current decisions
Routing stays as an option, off by default (source).
## Tasks
[x] T1: Capture discussion verbatim
[ ] T2: Make resume read the summary first
## Next action
Implement T2.
3. A small retrieval index. New records start with the short envelope shown above. The helper skills/shiplog/scripts/shiplog-read.sh returns those compact fields first, and full text only when the question needs it:
bash
shiplog-read.sh index # one line per open issue and PR: kind, tasks, labels, title, summary
shiplog-read.sh show 42 # #42's envelope, computed tasks, open tasks, one line per enveloped comment
shiplog-read.sh source 42 # exact text of the kind: source comments on #42
shiplog-read.sh search "auth" # matching issues, PRs, and local commits, one line each
Add -R OWNER/REPO before the command to read another repository. Task counts are computed from the checkboxes; no copies of derived state are stored. Only records from accounts GitHub marks as OWNER, MEMBER, or COLLABORATOR count as project records; envelopes from anyone else are shown as untrusted, with author and link only. Byte and API-call measurements for the helper are in tests/reader/MEASUREMENTS.md.
## A day with it
1. "Save this idea": the discussion becomes an issue with a source entry. No branch needed.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/devallibus-shiplog/)
- Source
- github · https://github.com/devallibus/shiplog
- Browse by field
- Open source
- Traction
- 56 ★
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.