Skip to content
cccskills
FreePublished on GitHub

commit

Create a conventional commit for all uncommitted changes

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68 stars(GitHub 68 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Commit: Create Conventional Commit

Process

1. Review changes

git status
git diff HEAD

2. Stage files

Add untracked and changed files. Be selective - never stage files that contain secrets (.env, credentials, etc.).

3. Pre-commit checks

  • If any .proto files changed: ./manage.py proto
  • If any Python files changed: ./manage.py lint -s backend
  • If any frontend files changed: ./manage.py lint -s ui

4. Create commit

Conventional commit format with a Uniffy domain scope:

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

<optional body with more detail>

Types: feat, fix, refactor, docs, test, chore, perf, style

Scopes (match domain directory names):

  • Backend domains: auth, users, organizations, groups, notes, files, calendar, projects, tasks, search, bookmarks, permissions, settings, attachments, agents, chat, calls, audit, platform, mail
  • Frontend features: same as backend, plus ui, theme, editor
  • Infrastructure: proto, db, worker, config, ci
  • Cross-cutting: core, shared

Examples:

feat(notes): add collaborative editing support
fix(calendar): correct timezone offset in recurring events
refactor(auth): extract token validation into shared utility
chore(proto): regenerate protobuf definitions

Rules

  • NEVER use emojis in commit messages
  • Keep the first line under 72 characters
  • Imperative mood ("add" not "added")
  • Changes spanning multiple domains: use the most significant one as scope
  • Add a body paragraph for complex changes explaining the why
  • NEVER include co-author information in the commit message

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create a Product Requirements Document from the current conversation and save it under `.agents/local/plans/`. Use when the user asks for a PRD, product specification, or requirements document for an Uniffy feature.

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68Updated Oct 23, 2026

Execute or resume an implementation plan from `.agents/local/plans/`, keeping its companion backlog and validation evidence current. Use when the user asks to implement a saved plan or continue planned multi-phase work.

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68Updated Oct 23, 2026

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68Updated Oct 23, 2026

Audit the in-tree model catalog against each provider's live API (Anthropic, OpenAI, Google, OpenRouter, xAI) using the keys in .env. Surfaces new models the catalog is missing, catalog models a provider no longer returns, and price/context drift on the curated OpenRouter subset, so the catalog stays current. Works on both stacks (docker containers or host venv). Run periodically or when a provider ships new models / changes pricing.

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68Updated Oct 23, 2026

Create a comprehensive Uniffy feature plan in `.agents/local/plans/` through deep codebase analysis, applicable rules, verified patterns, risks, tests, and executable validation steps. Use when the user asks to plan a feature or prepare implementation work without writing product code.

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68Updated Oct 23, 2026

pr

Free

Check the current branch for an existing PR and either update or create one with an auto-generated description based on all commits since diverging from main.

The English summary is being prepared. Showing the original description.

uniffy-io/uniffy68Updated Oct 23, 2026

See all skills by uniffy-io

Report a problem with this skill