cursor-git-integration
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-git-integrationManage integrate Git workflows with Cursor IDE. Triggers on "cursor git", "git in cursor", "cursor version control", "cursor commit", "cursor branch". Use when working with cursor git integration functionality. Trigger with phrases like "cursor git integration", "cursor integration", "cursor".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
35%This skill provides a skeletal outline of Cursor Git integration but lacks the concrete, actionable guidance needed for effective use. The instructions are too abstract (e.g., 'Use AI to generate commit messages' without showing how), and critical content is deferred to external files without providing meaningful quick-start examples. The skill describes what can be done rather than instructing how to do it.
Suggestions
Add concrete examples showing actual AI-generated commit message workflows, including the exact prompts to use and expected output format
Include executable code or specific command sequences for common tasks like conflict resolution with @git
Replace the vague 'Output' section with a concrete example showing before/after of a typical workflow
Add validation steps such as 'Verify commit message follows conventional commits format before pushing'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary sections like 'Prerequisites' that explain things Claude already knows (Git installed, basic understanding of Git workflows). The 'Output' section lists vague outcomes rather than concrete results. | 2 / 3 |
Actionability | Instructions are vague and lack concrete guidance. 'Use AI to generate commit messages' and 'Use @git in chat for AI-assisted reviews' provide no executable examples, specific commands, or expected outputs. No code snippets or copy-paste ready content. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. No guidance on what to do if commit message generation fails, how to verify changes were pushed correctly, or how to handle conflicts. The workflow is superficial. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present but the main content is too thin - it defers critical information (examples, error handling) without providing enough substance in the overview. The {baseDir} placeholder suggests incomplete templating. | 2 / 3 |
Total | 7 / 12 Passed |
Activation
40%This description suffers from a grammatically broken opening ('Manage integrate') and lacks specific concrete actions. While it attempts to provide trigger terms and a 'Use when' clause, the overly generic trigger 'cursor' undermines distinctiveness, and the absence of actual capability details (what git operations it supports) makes it difficult for Claude to know when this skill is truly appropriate.
Suggestions
Fix the grammar and list specific concrete actions: 'Manages Git workflows in Cursor IDE: commit changes, create branches, view diffs, resolve merge conflicts, push/pull from remotes.'
Remove the overly generic 'cursor' trigger and replace with more specific phrases like 'cursor staging', 'cursor git diff', 'cursor merge'.
Strengthen the 'Use when' clause with specific scenarios: 'Use when the user wants to perform version control operations within Cursor IDE, such as committing code, switching branches, or viewing git history.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage integrate Git workflows' without listing concrete actions. No specific capabilities are mentioned (e.g., commit, push, pull, branch creation). | 1 / 3 |
Completeness | Has a 'Use when' clause and trigger phrases, but the 'what' portion is extremely weak - 'Manage integrate Git workflows' is grammatically broken and doesn't explain actual capabilities. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'cursor git', 'cursor commit', 'cursor branch', but the final trigger 'cursor' alone is overly generic and would cause false matches. Missing common variations like 'version control', 'staging', 'push', 'pull'. | 2 / 3 |
Distinctiveness Conflict Risk | The Cursor IDE focus provides some distinction, but the generic trigger 'cursor' would conflict with any other Cursor-related skills. 'Git workflows' is also broad enough to overlap with general git skills. | 2 / 3 |
Total | 7 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.