Adoption

Agent Skills are supported by leading AI development tools.

VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory VS Code Gemini CLI GitHub Goose Amp Cursor Claude Code Letta OpenCode Claude OpenAI Codex Factory

coalesce-labs/commit

Name: commit
Author: coalesce-labs

plugins/dev/skills/commit/SKILL.md

npx skillsauth add coalesce-labs/catalyst commit

Clean

TrivyContainer and dependency vulnerability scanner

Clean

SemgrepStatic code analysis for vulnerabilities

Clean

mcp-scan (Snyk)Model Context Protocol security validation

Skipped

Snyk (dep)Open source security scanning

Skipped

Socket.devSupply chain security analysis

Skipped

VirusTotalMulti-engine malware detection

Skipped

CrowdStrikeAdvanced threat intelligence

Skipped

OSV-ScannerOpen Source Vulnerability database check

Skipped

OWASP Dep-Check

Commit Changes

You are tasked with creating git commits using conventional commit format for the changes made during this session.

Process:

Analyze what changed:
- Review the conversation history and understand what was accomplished
- Run git status to see current changes
- Run git diff --cached to see staged changes (if any)
- Run git diff to see unstaged changes
- Get changed file list: git diff --name-only and git diff --cached --name-only
Auto-detect conventional commit components:

Type detection (suggest to user):
- If only *.md files in docs/: suggest docs
- If only test files (*test*, *spec*): suggest test
- If package.json, *.lock files: suggest build
- If .github/workflows/: suggest ci
- If mix of changes: suggest feat or fix based on context
- Otherwise: ask user to choose from: feat, fix, refactor, chore, docs, style, perf, test, build, ci
Scope detection (suggest to user):
- Parse changed file paths
- Map to scopes:
  - agents/*.md → agents
  - commands/*.md → commands
  - scripts/* → scripts
  - docs/*.md → docs
  - .claude/ → claude
  - Multiple dirs or root files → empty scope (cross-cutting)
Extract ticket reference:
- Get current branch: git branch --show-current
- Extract ticket pattern: {PREFIX}-{NUMBER} (e.g., ENG-123, PROJ-456)
- Will be added to commit footer

Generate conventional commit message:

Format:

<type>(<scope>): <short summary>

<body - optional but recommended>

<footer - ticket reference>

Rules:

Header max 100 characters
Type: lowercase
Subject: imperative mood, no period, no capital first letter
Body: explain WHY, not what (optional for simple changes)
Footer: Refs: TICKET-123 if ticket in branch name

Example:

feat(commands): add conventional commit support to /commit

Updates the commit command to automatically detect commit type
and scope from changed files, following conventional commits spec.
Extracts ticket references from branch names for traceability.

Refs: ENG-123

Present plan to user:
- Show detected type and scope with confidence
- Show generated commit message
- Explain: "Detected changes suggest: <type>(<scope>): <summary>"
- List files to be committed
- Ask: "Proceed with this commit? [Y/n/e(dit)]"
  - Y: execute as-is
  - n: abort
  - e: allow user to edit message
Execute commit:
- Stage files: git add <specific-files> (NEVER use -A or .)
- Create commit with message
- Show result: git log --oneline -n 1
- Show summary: git show --stat HEAD

Configuration

Reads from .catalyst/config.json:

{
  "catalyst": {
    "commit": {
      "useConventional": true,
      "scopes": ["agents", "commands", "scripts", "docs", "config"],
      "autoDetectType": true,
      "autoDetectScope": true,
      "requireBody": false
    },
    "project": {
      "ticketPrefix": "PROJ"
    }
  }
}

Type Reference

Types that appear in CHANGELOG:

feat - New feature
fix - Bug fix
perf - Performance improvement
revert - Revert previous commit

Internal types:

docs - Documentation only
style - Formatting, no code change
refactor - Code restructuring, no behavior change
test - Adding/updating tests
build - Build system or dependencies
ci - CI/CD configuration
chore - Maintenance tasks

Examples

Feature:

feat(agents): add codebase-pattern-finder agent

Implements new agent for finding similar code patterns across
the codebase with concrete examples and file references.

Refs: ENG-456

Fix:

fix(commands): handle missing PR template gracefully

Previously crashed when thoughts/shared/pr_description.md was
missing. Now provides clear error with setup instructions.

Refs: ENG-789

Documentation:

docs(scripts): add README for setup scripts

Documents all scripts in scripts/ directory with usage examples
and explains when to use each setup method.

Refs: ENG-012

Chore (no ticket):

chore(config): update conventional commit scopes

Adds new scopes for agents and commands directories.

Important:

NEVER add co-author information or Claude attribution
Commits should be authored solely by the user
Do not include any "Generated with Claude" messages
Do not add "Co-Authored-By" lines
Write commit messages as if the user wrote them
Use conventional format for consistency and changelog generation
Keep header under 100 characters
Use imperative mood: "add feature" not "added feature"

Remember:

You have the full context of what was done in this session
Group related changes together logically
Keep commits focused and atomic when possible
The user trusts your judgment - they asked you to commit
Suggest type and scope based on file analysis
Extract ticket from branch name automatically
Allow user to override suggestions

coalesce-labs/commit

plugins/dev/skills/commit/SKILL.md

Automatically analyzes code changes and creates git commits with conventional commit messages when the user indicates they want to save their work, commit changes, or says 'commit this', 'save my changes', 'let's commit'. Auto-detects commit type, scope, and ticket reference from branch name.

10 stars

development

Updated May 1, 2026

$ install --global

skillsauth

npx skillsauth add coalesce-labs/catalyst commit

Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.

Security Scan Results

3 of 9 scanners reported clean

Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.

Scanners Passed

Scanners in report

Clean

TrivyContainer and dependency vulnerability scanner

95%

Clean

SemgrepStatic code analysis for vulnerabilities

95%

Clean

mcp-scan (Snyk)Model Context Protocol security validation

95%

Skipped

Snyk (dep)Open source security scanning

50%

Skipped

Socket.devSupply chain security analysis

50%

Skipped

VirusTotalMulti-engine malware detection

50%

Skipped

CrowdStrikeAdvanced threat intelligence

50%

Skipped

OSV-ScannerOpen Source Vulnerability database check

50%

Skipped

OWASP Dep-Check

50%

Last scanned: May 1, 2026, 3:11 AM188.7s1 file scanned

SKILL.md

name:: commit
disable-model-invocation:: false
allowed-tools:: Bash, Read
version:: 2.0.0

Commit Changes

You are tasked with creating git commits using conventional commit format for the changes made during this session.

Process:

Analyze what changed:
- Review the conversation history and understand what was accomplished
- Run git status to see current changes
- Run git diff --cached to see staged changes (if any)
- Run git diff to see unstaged changes
- Get changed file list: git diff --name-only and git diff --cached --name-only
Auto-detect conventional commit components:

Type detection (suggest to user):
- If only *.md files in docs/: suggest docs
- If only test files (*test*, *spec*): suggest test
- If package.json, *.lock files: suggest build
- If .github/workflows/: suggest ci
- If mix of changes: suggest feat or fix based on context
- Otherwise: ask user to choose from: feat, fix, refactor, chore, docs, style, perf, test, build, ci
Scope detection (suggest to user):
- Parse changed file paths
- Map to scopes:
  - agents/*.md → agents
  - commands/*.md → commands
  - scripts/* → scripts
  - docs/*.md → docs
  - .claude/ → claude
  - Multiple dirs or root files → empty scope (cross-cutting)
Extract ticket reference:
- Get current branch: git branch --show-current
- Extract ticket pattern: {PREFIX}-{NUMBER} (e.g., ENG-123, PROJ-456)
- Will be added to commit footer

Generate conventional commit message:

Format:

<type>(<scope>): <short summary>

<body - optional but recommended>

<footer - ticket reference>

Rules:

Header max 100 characters
Type: lowercase
Subject: imperative mood, no period, no capital first letter
Body: explain WHY, not what (optional for simple changes)
Footer: Refs: TICKET-123 if ticket in branch name

Example:

feat(commands): add conventional commit support to /commit

Updates the commit command to automatically detect commit type
and scope from changed files, following conventional commits spec.
Extracts ticket references from branch names for traceability.

Refs: ENG-123

Present plan to user:
- Show detected type and scope with confidence
- Show generated commit message
- Explain: "Detected changes suggest: <type>(<scope>): <summary>"
- List files to be committed
- Ask: "Proceed with this commit? [Y/n/e(dit)]"
  - Y: execute as-is
  - n: abort
  - e: allow user to edit message
Execute commit:
- Stage files: git add <specific-files> (NEVER use -A or .)
- Create commit with message
- Show result: git log --oneline -n 1
- Show summary: git show --stat HEAD

Configuration

Reads from .catalyst/config.json:

{
  "catalyst": {
    "commit": {
      "useConventional": true,
      "scopes": ["agents", "commands", "scripts", "docs", "config"],
      "autoDetectType": true,
      "autoDetectScope": true,
      "requireBody": false
    },
    "project": {
      "ticketPrefix": "PROJ"
    }
  }
}

Type Reference

Types that appear in CHANGELOG:

feat - New feature
fix - Bug fix
perf - Performance improvement
revert - Revert previous commit

Internal types:

docs - Documentation only
style - Formatting, no code change
refactor - Code restructuring, no behavior change
test - Adding/updating tests
build - Build system or dependencies
ci - CI/CD configuration
chore - Maintenance tasks

Examples

Feature:

feat(agents): add codebase-pattern-finder agent

Implements new agent for finding similar code patterns across
the codebase with concrete examples and file references.

Refs: ENG-456

Fix:

fix(commands): handle missing PR template gracefully

Previously crashed when thoughts/shared/pr_description.md was
missing. Now provides clear error with setup instructions.

Refs: ENG-789

Documentation:

docs(scripts): add README for setup scripts

Documents all scripts in scripts/ directory with usage examples
and explains when to use each setup method.

Refs: ENG-012

Chore (no ticket):

chore(config): update conventional commit scopes

Adds new scopes for agents and commands directories.

Important:

NEVER add co-author information or Claude attribution
Commits should be authored solely by the user
Do not include any "Generated with Claude" messages
Do not add "Co-Authored-By" lines
Write commit messages as if the user wrote them
Use conventional format for consistency and changelog generation
Keep header under 100 characters
Use imperative mood: "add feature" not "added feature"

Remember:

You have the full context of what was done in this session
Group related changes together logically
Keep commits focused and atomic when possible
The user trusts your judgment - they asked you to commit
Suggest type and scope based on file analysis
Extract ticket from branch name automatically
Allow user to override suggestions

Related Skills

coalesce-labs/migrate-dual-harness

development

VerifiedTrustedCommunity

Migrate a single-harness repo to the dual-harness layout so both Claude Code and Codex load the same instructions and skills — AGENTS.md as the portable canonical doc, a thin CLAUDE.md `@AGENTS.md` bridge, and a `.agents/skills` dir with a `.claude/skills` symlink onto it. Use when asked to migrate to dual-harness, make this repo work in both Claude and Codex, or for agent metadata cleanup.

17SKILL.mdUpdated Jul 27, 2026

coalesce-labs/migrate-dual-harness

coalesce-labs/recovery-pass

tools

VerifiedTrustedCommunity

Goal-driven senior-engineer pipeline-unstick sweep (CTL-1176 rung 3). Given the stuck/failed/needs-human set (or ONE ticket handed by the recovery router), its GOAL is to get the pipeline MOVING again — not to fix one ticket's review findings (that is phase-remediate). It runs AFTER the eyes (diagnostician evidence) and the hands (deterministic unstuck-sweep seams) have already tried, and it CONSUMES their output from a recovery-pass.json brief rather than re-diagnosing or redoing their narrow work. It acts like a senior engineer with full tool access — it resolves merge conflicts, rebases, force-pushes, merges green PRs, and re-dispatches stalled phases AUTONOMOUSLY — and escalates to the operator ONLY for a genuine value judgment / something that degrades other functionality / a real cost-benefit trade-off / a serious architecture change / an ADR conflict. On escalation it AUTHORS the operator inbox row + the push notification (executive-voiced). Dispatched as a `claude --bg` job by phase-agent-dispatch via slash command, AND invocable bare by the operator as a sweep — hence `user-invocable: true`. Ships behind CATALYST_RECOVERY_PASS (off by default — no live behavior change until shadow/enforce).

17SKILL.mdUpdated Jun 18, 2026

coalesce-labs/recovery-pass

coalesce-labs/setup-catalyst

tools

VerifiedTrustedCommunity

Diagnose and fix Catalyst setup issues. Validates tools, database, config, OTel, direnv, and thoughts. Automatically fixes what it can — creates directories, initializes the database, sets WAL mode, runs migrations. Use for new installs, upgrades, or when something isn't working.

17SKILL.mdUpdated Jun 7, 2026

coalesce-labs/setup-catalyst

coalesce-labs/plugins/dev/skills/phase-triage

tools

VerifiedTrustedCommunity

--- name: phase-triage description: Phase agent that triages a Linear ticket — expands acronyms, classifies (feature/bug/docs/refactor/chore), identifies genuine blockers (a semantic second-pass over the backlog — NOT a prose scrape; CTL-838), estimates scope, writes triage.json, and posts a triage analysis comment to Linear. Triage completion is signaled by that comment plus the local triage.json — there is no `triaged` label. Emits phase.triage.complete.<TICKET> on success and phase.triage.fai

17SKILL.mdUpdated May 18, 2026

coalesce-labs/plugins/dev/skills/phase-triage

Download

For Claude Desktop. Download once, then upload the file in the app — no terminal needed.

Need help? View full Cowork setup guide →

Install manually

Choose your platform

# Clone the repo
git clone https://github.com/coalesce-labs/catalyst.git

# Copy into Claude Code skills folder (global)
cp -r catalyst/plugins/dev/skills/commit ~/.claude/skills/

Claude Code Skills — official skills path docs.

Repository

coalesce-labs/catalyst

10 stars

Compatible with

Claude Code

OpenAI Codex CLI

ChatGPT