Run any Skill in Manus with one click

$pwd:

commit

Name: Commit
Author: elianiva

// Conventional commit message generator for jj and git repos. Analyzes diffs and produces scoped, well-formed commit messages. Use whenever the user says "commit", "make a commit", "write commit message", or similar.

Run Skill in Manus

$ git log --oneline --stat

stars:202

forks:9

updated:May 28, 2026 at 00:41

SKILL.md

readonly

name	commit
description	Conventional commit message generator for jj and git repos. Analyzes diffs and produces scoped, well-formed commit messages. Use whenever the user says "commit", "make a commit", "write commit message", or similar.

Commit Skill

Detection

# returns "jj" or "git"
which jj 2>/dev/null && jj root 2>/dev/null && echo "jj" || (git rev-parse --show-toplevel 2>/dev/null && echo "git")

Prefer jj if both work — it's the user's primary VCS.

jj

Check state

jj status           # changed files
jj diff             # full diff
jj diff <file>      # specific file

Commit (set message on working copy)

jj describe -m "<type>(<scope>): <subject>"

With body:

jj describe -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<body>
EOF
)"

Drop unrelated files before committing

jj restore --from @- <file1> <file2>

Git

git status                       # check state
git diff HEAD                    # all changes
git add <file>                   # stage
git commit -m "<type>(<scope>): <subject>"
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<body>
EOF
)"

Conventional Commit Format

<type>(<scope>): <subject>

<body>

Types: feat fix refactor perf style test docs chore revert

Scope: module changed, 1-2 words

Subject: imperative, no period, ≤72 chars

Body (optional): what and why, not how (diff shows how)

Breaking: add ! after type — feat!(api): change pagination response

Writing the Message

Read jj diff / git diff — understand every change
Identify primary intent — feat? fix? refactor?
Pick type + scope from that
Skim each hunk — if any doesn't serve the primary intent, flag it
Write imperative subject — "add X", "remove Y", "fix Z in W"
Body only when why isn't obvious — platform quirk, perf trade-off, migration step

Examples

✅ Right

Change	Message
New API route	`feat(flights): add GET /api/flights/:id`
Modal bug	`fix(responsive-modal): stop blurring select on mobile after scroll`
Rename function	`refactor(utils): rename fetchWrapper to useFetchWrapper`
Bump dep	`chore(deps): bump radix-ui/react-select to 2.2.6`
Remove dead code	`chore(auth): remove legacy session shim`
Perf	`perf(table): memoize row renderer`
Breaking change	`refactor!(db): drop legacy fuel_storage table`

❌ Wrong

Message	Why
`fix: fix bug`	Zero info
`fixed the modal`	Past tense, no scope
`fix(modal):fixed`	Missing space after colon
`feat(auth): add login page with form validation, error handling, remember-me, password reset, OAuth buttons`	Subject >72 chars
`fix(cache): change gcTime from 5min to 30min in queryClient config`	Describes how (diff shows it), not why
`✨ feat(ui): add spinner`	Emojis are noise in terminal
`fix #1234`	No description
`Bump lodash to 4.17.21 (#4567)`	GitHub auto-suffix noise

Rules

One logical change per commit — drop unrelated files before committing
Don't commit stray pnpm-lock.yaml — restore them out unless the change intentionally modifies deps
Don't use git add . / jj restore blindly — check what's in working copy first
Don't write subjects longer than 72 chars — body exists for details
Don't omit scope — fix: ... is ambiguous, fix(tooltip): ... is not
Don't use chore: wip — either write a meaningful subject or leave undescribed

related-skills.json

same repository

deslop.md

from "elianiva/dotfiles"

Remove all AI-generated slop like useless comments, try/catch blocks, and casts

2026-05-28202

agent-browser.md

from "elianiva/dotfiles"

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

2026-05-18202

caveman.md

from "elianiva/dotfiles"

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

2026-05-18202

opentui.md

from "elianiva/dotfiles"

Build terminal UIs with OpenTUI. Covers the core API, keymaps, React and Solid bindings, components, layout, keyboard input, plugins, and testing.

2026-05-18202

qa.md

from "elianiva/dotfiles"

Generate test cases in standard QA format.

2026-05-18202

pi-improvements.md

from "elianiva/dotfiles"

When encountering pi tool limitations, propose focused extensions that solve one problem each.

2026-04-13202

package.json

"author": "elianiva"

"repository": "elianiva/dotfiles"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	commit
description	Conventional commit message generator for jj and git repos. Analyzes diffs and produces scoped, well-formed commit messages. Use whenever the user says "commit", "make a commit", "write commit message", or similar.

Commit Skill

Detection

# returns "jj" or "git"
which jj 2>/dev/null && jj root 2>/dev/null && echo "jj" || (git rev-parse --show-toplevel 2>/dev/null && echo "git")

Prefer jj if both work — it's the user's primary VCS.

jj

Check state

jj status           # changed files
jj diff             # full diff
jj diff <file>      # specific file

Commit (set message on working copy)

jj describe -m "<type>(<scope>): <subject>"

With body:

jj describe -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<body>
EOF
)"

Drop unrelated files before committing

jj restore --from @- <file1> <file2>

Git

git status                       # check state
git diff HEAD                    # all changes
git add <file>                   # stage
git commit -m "<type>(<scope>): <subject>"
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>

<body>
EOF
)"

Conventional Commit Format

<type>(<scope>): <subject>

<body>

Types: feat fix refactor perf style test docs chore revert

Scope: module changed, 1-2 words

Subject: imperative, no period, ≤72 chars

Body (optional): what and why, not how (diff shows how)

Breaking: add ! after type — feat!(api): change pagination response

Writing the Message

Read jj diff / git diff — understand every change
Identify primary intent — feat? fix? refactor?
Pick type + scope from that
Skim each hunk — if any doesn't serve the primary intent, flag it
Write imperative subject — "add X", "remove Y", "fix Z in W"
Body only when why isn't obvious — platform quirk, perf trade-off, migration step

Examples

✅ Right

Change	Message
New API route	`feat(flights): add GET /api/flights/:id`
Modal bug	`fix(responsive-modal): stop blurring select on mobile after scroll`
Rename function	`refactor(utils): rename fetchWrapper to useFetchWrapper`
Bump dep	`chore(deps): bump radix-ui/react-select to 2.2.6`
Remove dead code	`chore(auth): remove legacy session shim`
Perf	`perf(table): memoize row renderer`
Breaking change	`refactor!(db): drop legacy fuel_storage table`

❌ Wrong

Message	Why
`fix: fix bug`	Zero info
`fixed the modal`	Past tense, no scope
`fix(modal):fixed`	Missing space after colon
`feat(auth): add login page with form validation, error handling, remember-me, password reset, OAuth buttons`	Subject >72 chars
`fix(cache): change gcTime from 5min to 30min in queryClient config`	Describes how (diff shows it), not why
`✨ feat(ui): add spinner`	Emojis are noise in terminal
`fix #1234`	No description
`Bump lodash to 4.17.21 (#4567)`	GitHub auto-suffix noise

Rules

One logical change per commit — drop unrelated files before committing
Don't commit stray pnpm-lock.yaml — restore them out unless the change intentionally modifies deps
Don't use git add . / jj restore blindly — check what's in working copy first
Don't write subjects longer than 72 chars — body exists for details
Don't omit scope — fix: ... is ambiguous, fix(tooltip): ... is not
Don't use chore: wip — either write a meaningful subject or leave undescribed

commit

Commit Skill

Detection

jj

Check state

Commit (set message on working copy)

Drop unrelated files before committing

Git

Conventional Commit Format

Writing the Message

Examples

✅ Right

❌ Wrong

Rules

More from this repository

Commit Skill

Detection

jj

Check state

Commit (set message on working copy)

Drop unrelated files before committing

Git

Conventional Commit Format

Writing the Message

Examples

✅ Right

❌ Wrong

Rules

More from this repository