git-workflow-pr-generator
Generate GitHub pull request descriptions by analyzing git changes between two branches. Use when the user asks to create or draft a PR description based on branch diffs (for example, "Generate a PR for the changes between featureBranch and mainBranch") and expects a filled template with summary, motivation, and change impact flags.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 clearly communicates what the skill does (generates PR descriptions from branch diffs), when to use it (user asks to create/draft a PR description), and what the output looks like (filled template with summary, motivation, change impact flags). The inclusion of a concrete example phrase further strengthens trigger matching and disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generate GitHub pull request descriptions', 'analyzing git changes between two branches', and specifies output details like 'filled template with summary, motivation, and change impact flags'. | 3 / 3 |
Completeness | Clearly answers both what ('Generate GitHub pull request descriptions by analyzing git changes between two branches') and when ('Use when the user asks to create or draft a PR description based on branch diffs') with explicit triggers and an illustrative example. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'pull request', 'PR description', 'branch diffs', 'Generate a PR', 'featureBranch', 'mainBranch'. The example phrase closely mirrors real user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets GitHub PR description generation from branch diffs with a template format. Unlikely to conflict with general git skills, commit message skills, or other documentation skills due to the precise scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with clear workflow steps and efficient use of tokens. Its main weaknesses are the lack of validation/error-handling checkpoints in the workflow (e.g., what if the script fails or produces empty output) and the missing bundle file for the referenced helper script. The heuristics for impact classification and the concrete template output are strong points.
Suggestions
Add validation checkpoints after step 2 (e.g., verify `pr_change_snapshot/` files exist and are non-empty before proceeding to classification)
Include error recovery guidance for common failure modes: script not found, empty diff (branches identical), or excessively large diffs
Provide the `scripts/collect_pr_changes.py` helper script in the bundle so the skill is self-contained and the reference is verifiable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what PRs are, what git diffs are, or other concepts Claude already knows. Every section serves a clear purpose—gathering inputs, classifying impacts, outputting the template. The heuristics for flag detection are concise and well-structured. | 3 / 3 |
Actionability | The skill provides a concrete script command (`scripts/collect_pr_changes.py <base> <head> --repo <path>`) and specific file paths, but the helper script itself is not included in the bundle. The heuristics for flag classification are specific and actionable, but the overall workflow relies on a script that cannot be verified. The template output is concrete and copy-paste ready, which is good. | 2 / 3 |
Workflow Clarity | The six steps are clearly sequenced and logically ordered. However, there are no validation checkpoints—no step to verify the script ran successfully, no check that the generated files exist or are non-empty before proceeding, and no error recovery guidance if the diff is too large or the script fails. For a multi-step workflow involving external script execution, this is a gap. | 2 / 3 |
Progressive Disclosure | The skill references a helper script in a Resources section, which is good structure. However, the bundle provides no actual files, so the reference to `scripts/collect_pr_changes.py` cannot be verified. The PR template is inline, which is appropriate since it's the core output. The content is reasonably organized but the template could arguably be in a separate file to keep the main skill leaner. | 2 / 3 |
Total | 9 / 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
- ucdavis/ai-skills-registry
- Commit
c0b2e4b
- 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.