Dipcode developer toolkit — git commit conventions, GitLab MR comment utilities, and dependency validation
This skill should be used when the user wants to commit changes to git — including requests like "commit my changes", "make a commit", "create a git commit", "commit this", "save my work to git", or any variation of "git commit". It also applies when the user says "save this", "write a commit message", "prepare a commit", or "checkpoint my work" and the intended output is a git commit. It enforces Conventional Commits format, includes issue key references when available, and prevents commits to protected branches (dev, main, master, release/*) by creating a working branch first.
This skill should be used when the user asks to "show MR comments", "fetch merge request comments", "list MR notes", "get GitLab MR review comments", "show merge request feedback", "display MR discussions", "what did reviewers say on my MR", "read MR review notes", "summarize MR comments", or mentions viewing, reading, or summarizing comments on a GitLab merge request.
This skill should be used when the user asks to "triage RT tickets", "triage the queue", "RT triage", "check RT queue", "find actionable tickets", "what tickets need attention", "which tickets are code-related", "review the support queue", "what tickets are waiting on us", "triage my tickets", "triage tickets owned by X", or mentions triaging, reviewing, or analyzing tickets from a Request Tracker (RT) queue against a codebase.
This skill should be used when the user asks to "validate a dependency", "check if this library is safe to use", "review a package before adding it", "audit a dependency", "check the license of a package", "is this library maintained", "evaluate a third-party library", "vet this dependency", "can I use this package commercially", "check dependency health", "should I use this library", "is this package secure", "dependency risk assessment", or mentions assessing the trustworthiness, license compliance, security posture, or maintenance status of a third-party package or library before adopting it.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A marketplace of plugins for AI-powered coding assistants — compatible with Cursor and Claude Code.
Each folder in this repository is a self-contained plugin that can be installed into your editor to extend its capabilities with custom skills, hooks, agents, and commands.
| Plugin | Description |
|---|---|
| devkit | Dipcode developer toolkit — git commit conventions and GitLab MR comment utilities |
Add and install from the marketplace:
# Add the marketplace
/plugin marketplace add [email protected]:dipcode-software/agents-marketplace.git
# Install a plugin
/plugin install devkit@dipcode-marketplace
To auto-suggest the marketplace for your team, add to .claude/settings.json:
{
"extraKnownMarketplaces": {
"dipcode-marketplace": {
"source": {
"source": "url",
"url": "[email protected]:dipcode-software/agents-marketplace.git"
}
}
}
}
To add this as a team marketplace:
Once imported, plugins can be installed directly from the marketplace panel, scoped to individual projects or system-wide.
The gitlab-mr-comments skill requires the following tools to be installed and available in your PATH:
python-gitlab — GitLab CLI (gitlab command):
pip install python-gitlab
Configure it via ~/.python-gitlab.cfg or environment variables. See the python-gitlab authentication docs for details.
jq — JSON processor used to normalize the API output:
# macOS
brew install jq
# Debian/Ubuntu
apt install jq
To add a new plugin, create a folder at the repository root containing:
.claude-plugin/plugin.json — Plugin manifest for Claude Code.cursor-plugin/plugin.json — Plugin manifest for Cursor (optional)skills/ — Skill definitions (markdown files with YAML frontmatter)hooks/ — Event-driven hooks (optional)agents/ — Autonomous agents (optional)commands/ — Slash commands (optional)Then register it in both marketplace files:
.claude-plugin/marketplace.json:
{
"name": "my-plugin",
"source": "./my-plugin",
"description": "What the plugin does"
}
.cursor-plugin/marketplace.json:
{
"name": "my-plugin",
"source": "my-plugin",
"description": "What the plugin does"
}
Note: Claude Code uses ./ prefixed relative paths, Cursor uses bare directory names.
Each plugin should be independent and self-contained. Plugins cannot reference files outside their own directory.
npx claudepluginhub dipcode-software/agents-marketplace --plugin devkitStreamline your git workflow with simple commands for committing, pushing, and creating pull requests
Creates git commits using conventional commit format with appropriate emojis, following project standards and creating descriptive messages that explain the purpose of changes.
Planning, committing, PR management, code polishing, action item extraction, and session handoffs.
Git workflow automation: conventional commits with branch protection, ticket tracking, and semantic correlation
Git and PR workflows with code review, onboarding, and PR enhancement
Ultra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.