commit-push

Stage + commit + push delegation a Haiku worker (token-cheap pattern, origen 2026-05-09). Orchestrator (Opus) prepara plan; Haiku ejecuta git workflow con guardrails verbatim. Activa: '/commit-push', 'commitea y sube', 'commit haiku', 'commit y push', 'commit + push'.

Quality

94%

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

88%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 highly actionable with a clearly sequenced, validated git delegation workflow and well-signaled external SSoT references. It is mostly lean, with minor redundancy from restating safety rules in both the prompt template and the anti-patterns section.

Suggestions

Consolidate the safety rules: the guardrails are restated verbatim in the prompt template and again in the Anti-patterns section — reference the SSoT once to trim tokens.

The bilingual Spanglish prose adds tokens without aiding execution; pick one language for prose narration while keeping the verbatim prompt template as-is.

Consider moving the full verbatim prompt template into a referenced file under references/ so the SKILL.md body stays a lean overview, improving progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no git fundamentals explained), but the mixed Spanglish and restating of the same safety rules in both the verbatim prompt template and the Anti-patterns section add some tokens that could be trimmed; noticeably above midpoint.	4 / 5
Actionability	Provides fully executable guidance — concrete bash commands (`git status --short`, `git branch --show-current`), a verbatim Agent spawn block, and an exact HEREDOC prompt template with precise reject conditions — copy-paste ready for the common cases.	5 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (pre-spawn audit rejecting wrong branch / secrets / clean tree) and failure-mode feedback loops in Step 4 (non-fast-forward, pre-commit hook, secret detected, branch mismatch — each with a re-spawn or escalate decision).	5 / 5
Progressive Disclosure	No bundle files exist; the body points to one-level-deep SSoT rule files (`.claude/rules/git-haiku-delegation.md`, `git-safety.md`, `parallel-safety.md`) clearly signaled at the top and in a Referencias section, with well-organized sections, though the verbatim prompt template is fairly long inline.	4 / 5
	Total	18 / 20 Passed

Description

100%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 concrete, trigger-rich, and complete, explicitly stating both the delegation workflow it performs and the natural phrases that activate it. It is highly distinctive with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Stage + commit + push delegation a Haiku worker', 'Orchestrator (Opus) prepara plan; Haiku ejecuta git workflow con guardrails verbatim' — giving comprehensive coverage of the delegation workflow rather than vague language.	5 / 5
Completeness	It explicitly answers both 'what' (stage + commit + push delegation to a Haiku worker with orchestrator preparing the plan) and 'when' via the explicit 'Activa:' trigger phrases.	5 / 5
Trigger Term Quality	The 'Activa:' clause provides comprehensive natural trigger phrases including synonyms across Spanish and English — '/commit-push', 'commitea y sube', 'commit haiku', 'commit y push', 'commit + push' — that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	It carves a clear niche — Haiku-delegated git commit/push with distinct triggers like '/commit-push' and 'commit haiku' — minimizing overlap with a generic git-commit skill.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alpacapurpura/luana-method
Path: claude/skills/commit-push/SKILL.md
Commit: caa08df

Reviewed: ~22 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.