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

84%

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

81%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, actionable skill body with a clear sequenced workflow, explicit validation, and a recovery feedback loop. The main improvements are reducing Steps/Commands redundancy and replacing the placeholder PR title with a more concrete generation step.

Suggestions

Collapse the overlap between the numbered Steps and the Commands block — either let Steps reference specific commands or merge the prose into command comments — to tighten conciseness.

Replace the `pr_title` placeholder with a concrete derivation step (e.g., summarize the diff subject line) or an explicit instruction so the command block is copy-paste ready.

Show an executable snippet for the PR-body draft/refresh against `.github/PULL_REQUEST_TEMPLATE.md` rather than leaving it as comment guidance.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with no over-explanation of git concepts, but the numbered Steps section rephrases much of what the Commands block already shows, a minor redundancy that could be trimmed; fits 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides concrete executable commands (`git push -u origin HEAD`, `gh pr create`, ruff/pytest gates), but the `pr_title="<clear PR title written for this change>"` placeholder and the comment-only PR-body draft workflow leave minor gaps, so it is mostly rather than fully executable.	4 / 5
Workflow Clarity	Steps 1–8 are explicitly sequenced with validation checkpoints (Step 2 pre-push validation, Step 7 PR-body placeholder check) and a feedback loop (Step 4: pull skill → resolve → re-validate → retry), and the destructive force-push is guarded by an explicit 'only when history was rewritten' condition, matching the top anchor.	5 / 5
Progressive Disclosure	Sections (Prerequisites, Goals, Related Skills, Steps, Commands, Notes) are well organized with one-level-deep, clearly signaled references (the `pull` skill, `.github/PULL_REQUEST_TEMPLATE.md`) and no nested references; the Steps/Commands overlap keeps it just short of a perfectly split overview.	4 / 5
	Total	17 / 20 Passed

Description

87%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 concise, well-targeted description that clearly answers both what the skill does and when to trigger it, with natural user language. Minor room to expand specificity and add PR-creation synonyms.

Suggestions

Add one or two more concrete actions (e.g., handle force-with-lease re-push, refresh existing PR body) to lift specificity toward 5.

Include common synonyms like 'open a PR' or 'submit a pull request' alongside 'create pull request' for fuller trigger coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Push current branch changes to origin and create or update the corresponding pull request' — two concrete actions (push, create/update PR) are named, but coverage stops at the core actions without enumerating related concrete steps, so it sits at 'several specific actions; minor gaps' rather than comprehensive.	4 / 5
Completeness	It explicitly states what it does ('Push current branch changes... create or update the corresponding pull request') and when to use it ('use when asked to push, publish updates, or create pull request') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Quotes 'use when asked to push, publish updates, or create pull request' — natural phrases a user would say are present ('push', 'publish updates', 'create pull request'), but common synonyms like 'open a PR' or 'submit PR' are missing, placing it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The push-and-PR niche is clearly scoped ('Push current branch changes to origin and create or update the corresponding pull request') with distinct triggers, and the push vs. pull boundary is explicit, giving minimal conflict risk.	5 / 5
	Total	18 / 20 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: c7f32d1

Reviewed: 1 day 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.