viv-commit-and-pr
Guides developers through standardized pull request creation workflow: auto-detects JIRA issue key(s) from the branch name, commits any uncommitted changes with the issue key(s) in the message, generates a descriptive PR title and body from the diff, and creates the pull request to a chosen target branch. Supports one or multiple JIRA keys (e.g. MBL-1327, POS-1123) and two modes — streamlined (auto-creates PR, default) and review (shows draft before creating). USE FOR: create PR, open pull request, make PR, submit PR, raise PR, create pull request, standardize PR workflow, PR with JIRA, commit and PR, push and create PR, create PR detailed, create PR full, create PR with review. DO NOT USE FOR: general git operations, branch creation, hotfix procedures unrelated to PR creation.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive trigger terms covering natural user language variations, explicit 'USE FOR' and 'DO NOT USE FOR' clauses, and clear boundaries that distinguish it from other git-related skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'auto-detects JIRA issue key(s) from branch name', 'commits uncommitted changes with issue key(s)', 'generates descriptive PR title and body from diff', 'creates pull request to chosen target branch'. Also specifies two operational modes (streamlined vs review). | 3 / 3 |
Completeness | Clearly answers both what (the workflow steps and capabilities) AND when with explicit 'USE FOR:' and 'DO NOT USE FOR:' clauses that provide comprehensive trigger guidance and boundary conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'create PR', 'open pull request', 'make PR', 'submit PR', 'raise PR', 'PR with JIRA', 'commit and PR', 'push and create PR'. Includes common variations and natural phrasing. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on PR creation workflow with JIRA integration. Explicitly excludes 'general git operations, branch creation, hotfix procedures' which helps prevent conflicts with other git-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, actionable skill with excellent workflow clarity and concrete executable guidance. The step-by-step process is well-sequenced with appropriate validation checkpoints and error handling. Minor weaknesses include some redundancy in mode detection explanations and the monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Remove the duplicate mode detection explanation—keep it in the Invocation Modes table and reference it from Step 1a rather than re-explaining
Consider moving the Error Handling Reference table and Conventions section to a separate REFERENCE.md file, keeping only a brief summary with a link in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy—the mode detection is explained multiple times (in Invocation Modes section and again in Step 1a), and some explanations could be tightened. The error handling table duplicates information already covered inline in the steps. | 2 / 3 |
Actionability | Excellent actionability with specific, executable git commands throughout, exact regex patterns for JIRA detection, precise prompt templates, and clear examples of user inputs and expected outputs. Every step has concrete commands to run. | 3 / 3 |
Workflow Clarity | Outstanding workflow structure with numbered steps, explicit validation checkpoints (verify git repo, validate JIRA format, check target branch exists, confirm commit success before push), clear conditional branching, and explicit stop conditions. The feedback loops for error recovery are well-defined. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and tables, but it's a monolithic document (~300 lines) that could benefit from splitting detailed reference material (like the error handling table and conventions) into separate files. The inline structure is good but everything is in one file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- vivekcse86/Awesome_Vscode_Skills_Agents
- Commit
2e44fab
- 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.