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.

2.05x

Quality

80%

Does it follow best practices?

Impact

80%

2.05x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/push/SKILL.md

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.

The content is well-structured, actionable, and includes explicit validation and feedback loops for a destructive-ish operation. Main improvement areas are tightening minor redundancy and making the PR-body authoring steps fully executable.

Suggestions

Make the PR-body authoring section executable (e.g. concrete gh pr edit --body-file invocation with template-driven content) instead of commentary placeholders.

De-duplicate the force-with-lease and sync-vs-auth guidance that appears in both Steps and Notes.

Consider mentioning the 'PR' synonym in the description trigger phrases to improve trigger term coverage.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge of git/PRs, with only minor redundancy between the Steps, Commands, and Notes sections (e.g. force-with-lease and sync-vs-auth guidance repeated) that could be trimmed.	4 / 5
Actionability	Provides concrete executable commands (git push -u origin HEAD, gh pr create/edit, mix pr_body.check), but the PR-body writing portion is commentary/placeholders rather than fully executable code.	4 / 5
Workflow Clarity	Eight clearly sequenced steps with explicit validation checkpoints (make -C elixir all, mix pr_body.check) and a feedback loop for rejected pushes (pull skill, re-validate, retry), plus checklist-style PR-state handling.	5 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled references (the pull skill, .github/pull_request_template.md) and no nested references; at ~110 lines it slightly exceeds the under-50 simple-skill exception.	4 / 5
	Total	17 / 20 Passed

Description

78%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 concise, third-person, and clearly answers both what the skill does and when to use it. Trigger terms are natural, though a few common synonyms (e.g. 'PR') would push it higher.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('Push current branch changes to origin' and 'create or update the corresponding pull request'), but does not list several specific actions needed for a 4.	3 / 5
Completeness	Explicitly answers both what (push branch changes, create/update PR) and when (asked to push, publish updates, or create pull request) with concrete trigger phrases.	5 / 5
Trigger Term Quality	'use when asked to push, publish updates, or create pull request' gives good natural trigger coverage, though common synonyms like 'PR' or 'open a PR' are missing.	4 / 5
Distinctiveness Conflict Risk	The push-plus-PR niche is mostly distinct with clear triggers, with only minor overlap risk against closely related git/pull skills.	4 / 5
	Total	16 / 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: openai/symphony
Path: .codex/skills/push/SKILL.md
Commit: 8001b52

Reviewed: 24 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.