push

Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

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 with strong workflow sequencing and validation feedback loops. The main weakness is redundancy between the prose Steps and the executable Commands sections.

Suggestions

Collapse the Steps section to focus on decision points and guardrails (force-with-lease, remote-auth handling, PR title reconsideration) instead of re-narrating the commands shown below, reducing overlap with the Commands block.

In the Commands block, replace the placeholder '' removal example with the actual placeholder strings expected by .github/PULL_REQUEST_TEMPLATE.md so the validation grep is copy-paste ready without inference.

Move the per-change PR-title guidance into the single place it applies (the gh pr create/edit commands) to avoid stating the title rules twice across Steps and Commands.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no basic git/gh explanations), but the prose Steps section largely narrates what the Commands block already shows, which could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready shell commands ('git push -u origin HEAD', 'gh pr create --title', 'ruff check app tests'); the title placeholder is appropriately justified per-change.	3 / 3
Workflow Clarity	Clear 8-step sequence with explicit validation checkpoints (pre-push validation in step 2, PR-body placeholder check in step 7) and a push-rejection feedback loop (pull skill → re-validate → retry).	3 / 3
Progressive Disclosure	Self-contained body with well-organized sections (Prerequisites, Goals, Related Skills, Steps, Commands, Notes); no nested references and no wall-of-text that should be split out, with no bundle files present.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that pairs concrete capabilities with an explicit 'use when' trigger clause. It is concise and clearly distinguishes the skill's niche from adjacent git operations.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Push current branch changes to origin and create or update the corresponding pull request' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Push current branch changes... create or update the corresponding pull request') and when ('use when asked to push, publish updates, or create pull request').	3 / 3
Trigger Term Quality	Includes natural terms users would actually say: 'use when asked to push, publish updates, or create pull request'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear push-and-PR niche with distinct triggers, unlikely to fire for the related pull/sync skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: karanhudia/borg-ui
Path: .codex/skills/push/SKILL.md
Commit: 380827d

Reviewed: 12 days 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.