Run any Skill in Manus with one click

caveman-commit

Stars24

Forks3

UpdatedJune 29, 2026 at 05:19

Write a Conventional Commit message in caveman style — terse subject, fragment body, full technical accuracy. Subject line stays a valid Conventional Commit (type: description). TRIGGER when: /caveman-commit invoked, or asked for a caveman commit message.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mifunedev

mifunedev/openharness

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	caveman-commit
description	Write a Conventional Commit message in caveman style — terse subject, fragment body, full technical accuracy. Subject line stays a valid Conventional Commit (type: description). TRIGGER when: /caveman-commit invoked, or asked for a caveman commit message.
argument-hint	[type]

Caveman Commit

Generate a commit message that obeys the harness commit format and caveman compression.

Read core rules first: .claude/skills/caveman/SKILL.md (drop/preserve + auto-clarity).

Rules

Subject: <type>: <description> per .claude/skills/git/SKILL.md — feat · fix · task · audit · skill. Imperative, lowercase, ≤50 chars, no trailing period. The subject must stay a legible Conventional Commit; compress the description words, not the structure.
Body (optional): fragment bullets, drop articles/filler. One line per logical change.
Preserve verbatim: file names, symbols, flags, issue/PR refs, breaking-change notes.
Do not caveman-ify the Co-Authored-By trailer or Closes # lines.

Example

fix: guard nil session in auth middleware

- add nil-check before token decode in authMiddleware
- return 401 not 500 on missing session
- covers panic from #287

Print the message only — do not run git commit unless the user asks.

More from this repository

same repository

delegate

mifunedev/openharness

TRIGGER when: asked to delegate work, execute or parallelize a plan, "run this plan", "delegate this", or after /prd or plan creation. Decomposes work by dependency, launches worker sub-agents in parallel waves, validates completion, and reports results while preserving failure isolation and recursion limits.

2026-07-1224

wiki

mifunedev/openharness

Dispatcher for the harness wiki knowledge base — routes the first token of $ARGUMENTS to one of three subcommands: ingest, query, or lint. The corpus lives at .oh/skills/wiki/corpus/ (entity pages) and corpus/raw/ (immutable snapshots), owned by this skill and gitignored-by-default (curated entries are whitelisted into git with `git add -f`). Canonical schema: .oh/skills/wiki/references/schema.md. Full per-subcommand procedures live in references/{ingest,query,lint}.md. Always logs per the Memory Improvement Protocol. TRIGGER when: "add to wiki", "capture this page", "snapshot this source", "ingest <url|path>", or promoting a sub-agent draft -> ingest; "what does the wiki say about X", "find wiki entries for X", "look up X in the wiki" -> query; "lint the wiki", "regenerate the wiki index", "find stale/orphaned wiki entries" -> lint.

2026-07-1024

blog

mifunedev/openharness

Turn a source scenario into a publishable blog post. First supported playbook: Loom/demo-to-blog, where a raw notes file plus Loom screenshots become a polished site post after Advisor briefing, photo/text alignment audit, site convention audit, narrative/fact-check audit, source-faithful image handling (exact URLs or local files downloaded from them), optional social/channel-promotion artifact generation, and build verification. Manual-invoke only because it writes content and may spawn delegates. TRIGGER when: /blog <scenario> invoked; asked to create a blog post from a Loom/video/demo/transcript/screenshots; asked to turn .claude/specs/<name>/ demo.md into an openharness-web blog post.

2026-07-0924

mifunedev/openharness

Start, inspect, or stop T3 Code (`npx t3`) in the Open Harness sandbox. Use this for the browser-based T3 Code harness on port 3773, including tmux launch, pairing URL discovery, logs, status, and shutdown. T3 Code wraps an already-authenticated Claude Code, Codex, or OpenCode backend. TRIGGER when: user asks to run T3 Code, start `npx t3`, open the T3 browser UI, get the T3 pairing URL, check T3 Code status/logs, or stop T3 Code.

2026-07-0724

retro

mifunedev/openharness

Scientific session-closing retrospective: scan the current conversation, turn each signal into a falsifiable hypothesis, cite session evidence for AND against it, assign a verdict (supported / refuted / inconclusive) and a confidence level, then promote only supported, sufficiently-confident hypotheses into the harness memory tiers (.oh/memory/MEMORY.md, .oh/context/IDENTITY.md) behind a propose-then-confirm gate. Reflects on six learning/knowledge subsystems through the lens of this session — continual learning, context compression, reinforcement learning, wiki, docs, and memory scaffolding — and points at the deep-dive lint/audit skills rather than running them. Operationalizes the Memory Improvement Protocol (.oh/skills/retro/references/memory-protocol.md) as an explicit, evidence-driven, session-closing skill rather than a per-run afterthought. Always appends a log entry. TRIGGER when: /retro invoked, or session closing with decisions, surprises, or failures worth preserving.

2026-07-0624

autopilot

mifunedev/openharness

Self-improvement loop: each hourly run implements the oldest open issue labeled `autopilot` that has no open PR. When the queue is empty it runs first-principles `/harness-audit` research, files its own `autopilot` ticket from the top-ranked finding, and builds that. Decomposes via the pm agent, then runs `/ship-spec --issue`, which owns the build end-to-end (the two compacts bracketing implement, a worktree Advisor, `/delegate` workers running `.oh/scripts/ralph.sh`, the `/eval` gate, and the `/pr-audit` promotable undraft) through to a ready-for-review PR whose description states why this item was selected. Harness-infra only (skills/rules/docs/scripts/crons/wiki) — never sandbox application code. Runs in its own per-run tmux session. Caps: 6 open autopilot PRs created per UTC day AND 10 total open; never auto-merges. TRIGGER when: the hourly .oh/crons/autopilot.md fires, or invoked manually on demand (e.g. /autopilot --dry-run to preview the next selection).

2026-07-0624

name	caveman-commit
description	Write a Conventional Commit message in caveman style — terse subject, fragment body, full technical accuracy. Subject line stays a valid Conventional Commit (type: description). TRIGGER when: /caveman-commit invoked, or asked for a caveman commit message.
argument-hint	[type]

Caveman Commit

Generate a commit message that obeys the harness commit format and caveman compression.

Read core rules first: .claude/skills/caveman/SKILL.md (drop/preserve + auto-clarity).

Rules

Subject: <type>: <description> per .claude/skills/git/SKILL.md — feat · fix · task · audit · skill. Imperative, lowercase, ≤50 chars, no trailing period. The subject must stay a legible Conventional Commit; compress the description words, not the structure.
Body (optional): fragment bullets, drop articles/filler. One line per logical change.
Preserve verbatim: file names, symbols, flags, issue/PR refs, breaking-change notes.
Do not caveman-ify the Co-Authored-By trailer or Closes # lines.

Example

fix: guard nil session in auth middleware

- add nil-check before token decode in authMiddleware
- return 401 not 500 on missing session
- covers panic from #287

Print the message only — do not run git commit unless the user asks.