git-manager

Git and GitHub workflow assistant for Nicolify (ap_sales_agent). Creates and manages branches, handles pull requests, resolves merge conflicts, generates changelogs, and manages releases and deployments. Use when the user asks to "create a branch", "sync with github", "push changes", "merge to main", "create a release", "make a PR", "resolve conflicts", "check git status", "deploy to production", "create a version", "write a changelog", or any git/GitHub related task. Also triggers on "quiero hacer un commit", "quiero pushear", "hacemos un release", "pasamos a producción", "nueva versión", "rama nueva".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and actionable with clean one-level references, but its destructive deploy-on-push workflow lacks an explicit pre-push validation gate, and a few gh command invocations and duplicated conventions could be tightened.

Suggestions

Add an explicit validation/test checkpoint (e.g. run tests, confirm green) before `git push origin main` in the `/git merge-main` flow, since a push to main triggers automatic production deploy.

Specify the flags for `gh pr create` and `gh release create` (e.g. `--title`, `--notes-file`) so the commands are copy-paste ready rather than underspecified.

De-duplicate the commit-convention format and branch rules between SKILL.md and references/git-strategy.md, keeping the body to a short pointer and the full detail in the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean — commands, numbered steps, and short bullets — and avoids explaining git concepts Claude already knows, though a few safety rules ('NUNCA crear feature branches') are restated across sections and could be trimmed.	4 / 5
Actionability	Mostly executable guidance with concrete git/gh commands and a worked conventional-commit format, but `gh pr create` and `gh release create` are named without their flag specifics, leaving minor gaps.	4 / 5
Workflow Clarity	Sequences are numbered with some validation ('Verificar que el código compila/arranca', test gate for releases), but the merge-to-production flow pushes to main (auto-deploy) without an explicit test/validation checkpoint before the destructive push, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	Good structure with real one-level-deep references (references/git-strategy.md, references/changelog-templates.md) and a clear Referencias section; minor gap is commit-convention content duplicated between the body and git-strategy.md.	4 / 5
	Total	15 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it enumerates concrete capabilities, provides rich bilingual trigger phrases, and clearly separates what from when. The only weakness is the broad fallback clause that slightly raises conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Creates and manages branches, handles pull requests, resolves merge conflicts, generates changelogs, and manages releases and deployments' — giving comprehensive capability coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what (the enumerated git/GitHub actions) and when ('Use when the user asks to ...') with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases ('make a PR', 'push changes', 'deploy to production', 'write a changelog') plus Spanish synonyms ('quiero pushear', 'pasamos a producción', 'nueva versión'), matching the top anchor's synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Mostly distinct with a clear Nicolify-scoped niche, but the catch-all 'or any git/GitHub related task' creates minor overlap risk with other generic git skills, so it sits just below the minimal-conflict anchor.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alpacapurpura/luana-method
Path: claude/skills/git-manager/SKILL.md
Commit: caa08df

Reviewed: ~21 hours ago

Table of Contents

Discovery Implementation Validation

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.