Cocogitto

Skill aldiipratama/dyy-plugin/skills/version-control/cocogitto

An advanced, universal developer plugin for the **Antigravity** coding environment. **dyy-plugin** packages dynamic developer rules, modular agent personas (subagents), and optimized conventional workflow scripts for seamless frontend, backend, and Linux window manager (ricing) customization.

Install

npx -y skills add aldiipratama/dyy-plugin --skill cocogitto

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Automates creating conventional commit messages validated by cocogitto (cog) for Git version control. Use when preparing to make commits or writing changelogs.

SKILL.md

2.3 KB, as published. Nobody here has run it

Cocogitto Git Commit Automation

Overview

This skill ensures that all commits made in this environment strictly adhere to the Conventional Commits specification as validated by the cocogitto (cog) tool. Clean commit histories enable automated versioning, release note generation, and automated changelogs.

Commit Message Format

Each commit message must follow this structure:

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

[optional body]

[optional footer(s)]

Types Allowed

feat: A new user-facing feature.
fix: A bug fix.
docs: Documentation changes only.
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.).
refactor: A code change that neither fixes a bug nor adds a feature.
perf: A code change that improves performance.
test: Adding missing tests or correcting existing tests.
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm).
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs).
chore: Other changes that don't modify src or test files.
revert: Reverts a previous commit.

Code Example / Command Usage

When making a commit, prefer using cog commit direct commands over standard git commit to ensure validation happens immediately:

# General commit format using cog
cog commit <type> "<description>"

# Example of a feature commit
cog commit feat "add user profile picture upload support"

# Example of a fix commit
cog commit fix "resolve memory leak in file watcher"

If committing via standard Git, make sure your message is structured properly:

git commit -m "feat: initialize retro-modern bspwm configuration with rice installer

- Centralize color themes in .chezmoidata/colors.toml (Catppuccin Mocha)
- Implement flat rectangle styling (corner-radius: 0) system-wide
- Add cocogitto config (cog.toml) to repository root"

Verification

Before finishing a git task, verify that the commits are compliant by running:

# Check if the commit history is compliant
cog check