multica/skills/commit/SKILL.md at f2ca86aa1f08ac92a22c3df919f05d697c9bbaf3

feat(agent): add skills system with profile integration (#21 )

* chore(deps): add yaml package for skill parsing

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* feat(agent): add skills system

Implement a skills system inspired by moltbot's approach:

- Skills are markdown files (SKILL.md) with YAML frontmatter
- Multi-source loading with precedence: bundled < user < workspace
- Eligibility filtering based on platform, binaries, and env vars
- Skills are automatically included in agent system prompt
- New AgentOptions: enableSkills, skillsBaseDir, extraSkillDirs

Includes two bundled skills:
- commit: Git commit helper with conventional commit guidelines
- code-review: Code review checklist and best practices

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* refactor(skills): use profile-based skills instead of workspace

Change skill loading from workspace-based (.skills/) to profile-based:
- Skills now load from ~/.super-multica/agent-profiles/<profileId>/skills/
- Remove workspace and user skill sources
- Simplify to only bundled and profile sources
- Profile skills have higher precedence than bundled

This is more appropriate for non-coding agents where skills are
associated with agent identity rather than working directory.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-30 05:21:57 +08:00

2.1 KiB

Raw Blame History

name

description

version

metadata

Git Commit Helper

Create well-formatted git commits following conventional commit standards

1.0.0

emoji

requiresBinaries

Instructions

When the user asks you to create a commit or commit their changes, follow these guidelines:

Step 1: Review Changes

Run git status to see what files have changed
Run git diff to see the actual changes
If there are staged changes, also run git diff --staged

Step 2: Analyze and Group Changes

Group related changes into logical commits:

Feature additions
Bug fixes
Refactoring (no functional change)
Documentation
Tests
Configuration/dependencies

Step 3: Create Atomic Commits

For each logical group of changes:

Stage only the relevant files: git add <file1> <file2>
Create a commit with conventional message format

Commit Message Format

Use conventional commits:

feat: New feature
fix: Bug fix
refactor: Code refactoring (no functional change)
docs: Documentation changes
test: Adding or updating tests
chore: Build, config, dependencies

Format: <type>(<scope>): <description>

Example: feat(auth): add user login endpoint

Rules

Each commit should be independently meaningful and buildable
Related test files should be committed with their implementation
Never create empty commits
Never combine unrelated changes in one commit
Keep commit messages concise but descriptive
If all changes are related to one logical unit, a single commit is fine

Example

If the user modified:

src/api/user.ts (added new endpoint)
src/api/user.test.ts (tests for new endpoint)
src/utils/format.ts (refactored helper)
README.md (updated docs)

Create three commits:

git add src/api/user.ts src/api/user.test.ts && git commit -m "feat(api): add user profile endpoint"
git add src/utils/format.ts && git commit -m "refactor(utils): simplify date formatting logic"
git add README.md && git commit -m "docs: update API documentation"

2.1 KiB Raw Blame History