Code Solving
HoangTheQuyen/think-better
Structured coding workflow for non-trivial code work: debug, build features, refactor, optimize, migrate and review code through 7 steps with evidence-based quality gates.
Pre-merge / pre-deploy gate. An agent skill from robertbarclayy/conducty.
Install Conducty Ship
$ npx skills add robertbarclayy/conducty --skill conducty-ship -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install robertbarclayy/conducty conducty-ship --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/robertbarclayy/conducty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/conducty-ship .claude/skills/conducty-ship && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "conducty-ship" agent skill from https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-ship into .claude/skills/conducty-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conducty-ship", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-shipType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add robertbarclayy/conducty --skill conducty-ship -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install robertbarclayy/conducty conducty-ship --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertbarclayy/conducty.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/conducty-ship .agents/skills/conducty-ship && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conducty-ship" agent skill from https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-ship into .agents/skills/conducty-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conducty-ship", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add robertbarclayy/conducty --skill conducty-ship -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install robertbarclayy/conducty conducty-ship --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertbarclayy/conducty.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/conducty-ship .cursor/skills/conducty-ship && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conducty-ship" agent skill from https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-ship into .cursor/skills/conducty-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conducty-ship", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/robertbarclayy/conducty.git --path skills/conducty-ship--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add robertbarclayy/conducty --skill conducty-ship -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install robertbarclayy/conducty conducty-ship --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertbarclayy/conducty.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/conducty-ship .gemini/skills/conducty-ship && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "conducty-ship" agent skill from https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-ship into .gemini/skills/conducty-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conducty-ship", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install robertbarclayy/conducty conducty-shipInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add robertbarclayy/conducty --skill conducty-ship -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/robertbarclayy/conducty.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/conducty-ship .github/skills/conducty-ship && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "conducty-ship" agent skill from https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-ship into .github/skills/conducty-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conducty-ship", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add robertbarclayy/conducty --skill conducty-ship -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install robertbarclayy/conducty conducty-ship --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/robertbarclayy/conducty.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/conducty-ship .opencode/skills/conducty-ship && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conducty-ship" agent skill from https://github.com/robertbarclayy/conducty/tree/main/skills/conducty-ship into .opencode/skills/conducty-ship/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conducty-ship", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
conducty-ship- GitHub stars
- 176
- Token cost
- ~1.9k tokens
- SKILL.md length
- 745 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Pre-merge / pre-deploy gate. An agent skill from robertbarclayy/conducty.
- Works in 7 steps: Read the Plan + Code Review → Resolve Project Commands → Run the Battery → …
- The user says ship it
- SKILL.md covers When to Use, The Battery, Workflow and Principles
- Calls git, cargo and npm
What it does
Conducty Ship is an agent skill from robertbarclayy/conducty. Pre-merge / pre-deploy gate. Runs the full ship-readiness battery — lint, typecheck, test suite, secrets scan, dependency-vulnerability check, [[conducty-code-review]] verdict — and writes a Ship Reports/Ship Report YYYY-MM-DD HHmm.md note with a single-word verdict. Use when the user says "ship it", "is this ready", "ship gate", "pre-merge check", "ready to merge", or after [[conducty-code-review]] passes.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review, Test generation and Quality gates. The repository describes itself as: Stop context-switching. Start batch-planning. Conducty replaces the fragmented cycle of plan → prompt → wait → get distracted → review → fix → repeat with advanced batch planning. The licence is MIT.
When your agent uses it
- The user says ship it
- Pre-merge check
- After [[conducty-code-review]] passes
Example prompts
- “ship it”
- “is this ready”
- “ship gate”
- “/conducty-ship”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 64aefd5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitcargonpmtscgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, npm and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Conducty Ship loads about 1.9k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 745 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from robertbarclayy/conducty at commit 64aefd5, republished under its MIT licence (© robertbarclayy). 745 words, ~1,915 tokens.
Download SKILL.mdSave it as
.claude/skills/conducty-ship/SKILL.md (or your agent's skills folder).- name
- conducty-ship
- description
- Pre-merge / pre-deploy gate. Runs the full ship-readiness battery — lint, typecheck, test suite, secrets scan, dependency-vulnerability check, [[conducty-code-review]] verdict — and writes a `Ship Reports/Ship Report YYYY-MM-DD HHmm.md` note with a single-word verdict. Use when the user says "ship it", "is this ready", "ship gate", "pre-merge check", "ready to merge", or after [[conducty-code-review]] passes.
- aliases
- conducty-ship, ship
- tags
- conducty/skill, conducty/ship, conducty/quality
Conducty Ship — The Pre-Merge Gate
[[conducty-checkpoint]] gates a parallelization group inside a plan. [[conducty-code-review]] gives a holistic human-style read of the branch. conducty-ship is the last gate before merge: it runs the actual mechanical checks every project must pass and produces a single ship-or-don't verdict.
[!important] Read [[conducty-obsidian]] first Output goes to the vault as
Ship Reports/Ship Report YYYY-MM-DD HHmm.md, linked from the plan note and the code-review note.
When to Use
- After [[conducty-code-review]] verdict is
passorneeds-fix(with fixes applied) - Before merging to main, opening a release PR, or deploying
- The user says "ship it", "ready to merge", "ship gate", "pre-merge check"
Skip when:
- The plan hasn't been reviewed yet — run [[conducty-code-review]] first
- The branch is not yet a candidate for merge (still mid-plan)
The Battery
Six gates. Every gate must pass for ship verdict to be green. A single failure in any gate produces verdict red. Yellow exists only for Code review: needs-fix with all fixes applied but not re-reviewed — flag it but treat operationally as red.
| # | Gate | What runs | Pass criterion |
|---|---|---|---|
| 1 | Code review | Read Code Reviews/Code Review YYYY-MM-DD HHmm.md from the vault | Verdict pass, or needs-fix with all Important/Critical findings checked off |
| 2 | Lint / format | Project's lint command (npm run lint, cargo clippy, ruff, etc.) | Exit 0, no warnings the project treats as errors |
| 3 | Type check | Project's typechecker (tsc --noEmit, mypy, cargo check) | Exit 0, no errors |
| 4 | Test suite | Full test suite (npm test, cargo test, pytest, etc.) | Exit 0, no failures, no skipped tests added in this branch |
| 5 | Secrets scan | git diff $(git merge-base HEAD main)..HEAD piped through a secret-pattern grep | No matches against secret patterns (API keys, tokens, credentials) |
| 6 | Dependency vulnerabilities | npm audit, pip-audit, cargo audit, osv-scanner, etc. — whichever fits the project | No new High/Critical vulns introduced by this branch's dependency changes |
Workflow
Step 1: Read the Plan + Code Review
From the active plan note, find the wikilinked Code Review YYYY-MM-DD HHmm note. Open it. If verdict is block, stop — the branch is not ship-eligible. If verdict is needs-fix, confirm every Critical/Important finding has been addressed (checkbox checked) before proceeding.
Step 2: Resolve Project Commands
Pull the project's commands from [[Context {Project} Tests]] and [[Context {Project} Conventions]] (see [[conducty-context]]). Required entries:
- Lint command
- Typecheck command (or "n/a" with justification — e.g. dynamically typed and the project doesn't run a checker)
- Test command
- Vulnerability check command
If any are missing, ask the user, run them, and ask the user to commit the answer to the project's context note before proceeding (so the next ship doesn't re-ask).
Show full SKILL.md (320 more words)Show less
Step 3: Run the Battery
Run gates 2-6 in parallel where possible (Bash with && and &, or sequential with concise output). Capture for each:
- Command run
- Exit code
- Pass/fail
- For failures: the exact failing line(s) — copy verbatim, don't paraphrase
For the secrets scan, use a conservative pattern set:
git diff $(git merge-base HEAD main)..HEAD | \
grep -inE '(api[_-]?key|secret|password|token|bearer|sk_live|sk_test|aws_access|private[_-]?key|-----BEGIN)' || \
echo "secrets: clean"Tune patterns to the project. False positives are acceptable — a human will check; false negatives are not.
Step 4: Compute Verdict
| Verdict | Condition |
|---|---|
| green | All 6 gates pass. Ship. |
| red | Any gate failed. Do not ship. |
| yellow | All mechanical gates pass, but code-review is needs-fix with fixes applied but not re-reviewed. Re-run [[conducty-code-review]] before merging. |
Step 5: Write the Ship Report
---
type: ship-report
date: YYYY-MM-DD
time: HHmm
project: {project-name}
branch: {branch-name}
base: {base-ref}
verdict: green | yellow | red
tags: [conducty, conducty/ship]
---
# Ship Report YYYY-MM-DD HHmm — {Branch}
## Verdict
**{green | yellow | red}** — {one-sentence rationale}
## Battery
| Gate | Result | Detail |
|------|--------|--------|
| Code review | {pass / needs-fix-applied / block} | [[Code Review YYYY-MM-DD HHmm]] |
| Lint | {pass / fail} | `{command}` exit {code} |
| Typecheck | {pass / fail / n/a} | `{command}` exit {code} |
| Test suite | {pass / fail} | `{command}` — {N} passed, {M} failed |
| Secrets scan | {pass / fail} | {pattern matches or "clean"} |
| Dep vulnerabilities | {pass / fail} | {new High/Critical CVEs or "clean"} |
## Failure Detail
<!-- For each red gate, paste the exact failing output (truncate sensibly).
Empty if verdict is green. -->
## Action
- **green**: ready to merge. Suggested next: open or merge the PR. Do not auto-merge — the user owns the ship action.
- **yellow**: re-run [[conducty-code-review]] on the post-fix branch.
- **red**: fix the failing gate(s). For test failures, generate a fix prompt via [[conducty-debug]] and slot it into the next plan or a remediation plan.
## Related
- Plan: [[Plan YYYY-MM-DD HHmm Topic]]
- Code review: [[Code Review YYYY-MM-DD HHmm]]
- Project context: [[Context {Project}]], [[Context {Project} Tests]]
- Patterns surfaced: [[Failure Patterns]]Step 6: Wire Wikilinks
- Edit the plan note's
## Review Notessection to add[[Ship Report YYYY-MM-DD HHmm]]. - Edit the code-review note's
## Relatedsection to add the same. - If verdict is red, prepend an entry to
[[Failure Patterns]]describing which gate failed and the leverage point ([[conducty-debug]]). Mechanical-gate failures are usually code-level; secrets-scan / vuln failures are usually plan-level (the prompt should have prevented them).
Step 7: Hand Off
- green: report verdict to user. Do not push, merge, or deploy autonomously — those are user-confirmed actions per Claude Code's blast-radius rules. Suggest the next command.
- yellow / red: present the failures and proposed next plan or fix prompts.
Principles
- Mechanical, not subjective — ship runs commands and reads exit codes. Subjective review is [[conducty-code-review]]'s job.
- All-or-nothing verdict — green/red, not 4-out-of-6. Yellow exists only for the post-review-fix re-run case.
- Failure detail is verbatim — copy the failing command output, never paraphrase. The user (or the next fix prompt) needs to see exactly what broke.
- Ship never auto-merges — verdict is advisory. The user runs
git merge/gh pr merge. - Every red gate is a learning — failures append to
[[Failure Patterns]]so the next plan's prompt-quality gate can prevent the smell that caused them. - Battery is project-specific but consistent — six gates always run; the commands come from the project's context notes.
© robertbarclayy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/conducty-ship of robertbarclayy/conducty.
Open the folder on GitHubat commit 64aefd5
Compare with similar skills
Conducty Ship next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conducty Ship this skillrobertbarclayy/conducty | 176 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Code SolvingHoangTheQuyen/think-better | 122 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Code Qualitywaybarrios/opencode-power-pack | 533 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Spec ReviewAI-Unified-Process/marketplace | 142 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Review Pre Commitopenwpm/OpenWPM | 1.4k | — | ~788 | Automated safety check: Pass | Custom licence | |
| Requesting Code ReviewHezaoHezao/poirot | 249 | 5 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Code Quality
waybarrios/opencode-power-pack
Agents should invoke this skill for code reviews, linting/formatting setup, maintainability checks, complexity concerns, warning cleanup, coding standards, or quality gates in Rust, TypeScript…
Spec Review
AI-Unified-Process/marketplace
Reviews the specification artifacts in docs/ (requirements, use case diagram, use case specifications, test cases, BPMN process models, entity model, glossary) against each other in two parts: a…
Review Pre Commit
openwpm/OpenWPM
Use as a pre-commit quality gate — review the working diff for stub patterns (TODO/FIXME/unimplemented!()/todo!()), debug leftovers (dbg!, stray console.log/println!, commented-out code), then run…
Requesting Code Review
HezaoHezao/poirot
Pre-commit review: security scan, quality gates, auto-fix. An agent skill from HezaoHezao/poirot.
Bench Baton
nooga/let-go
Coordinate heavy local workloads across worktrees, processes, and subagents — benchmarks and timing-sensitive gates run exclusively on a quiesced machine, while builds, test suites, regeneration…
More from robertbarclayy/conducty
All 20 skills in this repoConducty Checkpoint
robertbarclayy/conducty
Quality gate between parallelization groups. An agent skill from robertbarclayy/conducty.
Conducty Code Review
robertbarclayy/conducty
Standalone post-implementation code review across a whole branch or PR.
Conducty Context
robertbarclayy/conducty
Ingest a project directory into the Obsidian vault as a linked context sub-graph — Architecture, Conventions, Invariants, Hotspots, Tests, Glossary, plus per-bounded-context module notes.
Conducty Debug
robertbarclayy/conducty
Leverage-point analysis for failed prompts. An agent skill from robertbarclayy/conducty.
Conducty Execute
robertbarclayy/conducty
Dispatches Claude Code Task subagents to run prompts from a vault plan note.
Conducty Improve
robertbarclayy/conducty
End-of-plan improvement kata. An agent skill from robertbarclayy/conducty.
Related
Categories
Questions about Conducty Ship
What does Conducty Ship do?
Pre-merge / pre-deploy gate. An agent skill from robertbarclayy/conducty. Conducty Ship is an agent skill from robertbarclayy/conducty. Pre-merge / pre-deploy gate.
When should I use Conducty Ship?
Conducty Ship fits situations like: the user says ship it; pre-merge check; after [[conducty-code-review]] passes.
How do I install Conducty Ship in Claude Code?
Run `npx skills add robertbarclayy/conducty --skill conducty-ship -a claude-code`. Or copy the skill folder (skills/conducty-ship in robertbarclayy/conducty) into .claude/skills/conducty-ship in your project. Claude Code loads it when a task matches its description.
How do I install Conducty Ship in Codex?
Run `npx skills add robertbarclayy/conducty --skill conducty-ship -a codex`. Or copy the skill folder (skills/conducty-ship in robertbarclayy/conducty) into .agents/skills/conducty-ship in your project. Codex loads it when a task matches its description.
Can I use Conducty Ship in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add robertbarclayy/conducty --skill conducty-ship -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conducty-ship, .gemini/skills/conducty-ship, .github/skills/conducty-ship and .opencode/skills/conducty-ship in your project.
What does Conducty Ship need to run?
Going by SKILL.md and its folder, Conducty Ship needs the command-line tools its instructions call (git, cargo, npm, tsc and gh).
Does Conducty Ship access the network?
SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Conducty Ship safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conducty Ship use?
Conducty Ship is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conducty Ship use?
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Conducty Ship?
Skills that share tags, products or a category with Conducty Ship: Code Solving (HoangTheQuyen/think-better, 122 stars), Code Quality (waybarrios/opencode-power-pack, 533 stars), Spec Review (AI-Unified-Process/marketplace, 142 stars) and Review Pre Commit (openwpm/OpenWPM, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conducty Ship?
robertbarclayy (a GitHub user) maintains it in robertbarclayy/conducty, which has 176 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on June 19, 2026.
Source: robertbarclayy/conducty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.