CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is git-manager in alpacapurpura/luana-method

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-structured, highly actionable skill body: concrete bash commands per sub-command, clear safety rules, and clean one-level-deep references to real bundle files. The main improvement areas are trimming duplicated rules and tightening validation into explicit feedback loops (validate → fix → retry) for the destructive merge/release paths.

Suggestions

Consolidate duplicated rules — state 'NUNCA crear feature branches' and the propose-a-version rule once (e.g., only in Reglas de Seguridad or only in the relevant command section) instead of repeating them across sections.

Add explicit feedback loops to /git merge-main and /git release: e.g., 'run tests → if failing, stop and report' before tagging/pushing, rather than relying on a generic rule elsewhere in the file.

DimensionReasoningScore

Conciseness

Direct commands with no tutoring on git basics, but there is real redundancy: "NUNCA crear feature branches" appears in both Contexto and the /git branch section, and the propose-a-version rule appears in both /git release and Reglas de Seguridad. Mostly efficient with minor trims possible — anchor 4, not 5.

4 / 5

Actionability

Copy-paste-ready commands throughout — `git checkout -b development main`, `git tag -a v<version> -m "Release v<version>"`, `gh pr create`, `gh release create`, `git push origin <rama-actual> --rebase` — covering each sub-command's common case, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Each sub-command has a numbered sequence with real checkpoints ("Verificar que el código compila/arranca" after conflict resolution, "verificar que los tests pasan antes de un release"). Not 5 because validation is not a closed feedback loop — no explicit if-fails-then-fix-and-retry cycle, and /git merge-main has no inline verification step before pushing.

4 / 5

Progressive Disclosure

A clear command-indexed overview with well-signaled, one-level-deep references: inline pointers ("> Ver formato extendido en `references/git-strategy.md`", "> Ver template completo de PR body en `references/git-strategy.md`", "ver templates en `references/changelog-templates.md`") plus a final Referencias section — and both referenced files exist in the bundle.

5 / 5

Total

18

/

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.

A strong description: concrete, third-person action list plus an explicit bilingual 'Use when' trigger clause. The only weakness is the generic "any git/GitHub related task" catch-all, which slightly raises conflict risk with other git-related skills.

DimensionReasoningScore

Specificity

Lists six concrete actions — "Creates and manages branches, handles pull requests, resolves merge conflicts, generates changelogs, and manages releases and deployments" — giving comprehensive coverage of the skill's capabilities with no gaps.

5 / 5

Completeness

Explicitly answers both "what" (the six concrete actions) and "when" ("Use when the user asks to 'create a branch', 'sync with github', ...") with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Extensive natural trigger phrases users would actually say, in both English ("make a PR", "push changes", "deploy to production", "write a changelog") and Spanish ("quiero pushear", "pasamos a producción", "nueva versión"), covering synonyms and colloquial variants.

5 / 5

Distinctiveness Conflict Risk

Scoped to a named project ("Nicolify (ap_sales_agent)") with distinct, specific triggers, but the catch-all "or any git/GitHub related task" broadens it and creates minor overlap risk with generic git helpers.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alpacapurpura/ap_sales_agent

Path

.claude/skills/git-manager/SKILL.md

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.