Skip to content
Skills Library
Programming · Automation

push

/push

Explicitly run the repository push workflow on the development branch only: build, run tests, stage and read the change, write a conventional commit message, commit, then push the development branch. Use only when the user clearly wants the commit-and-push workflow. Do not trigger implicitly for ordinary coding or review tasks.

Licence
MIT
Last repository change
04.11.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Explicitly run the repository push workflow on the development branch only: build, run tests, stage and read the change, write a conventional commit message, commit, then push the development branch. Use only when the user clearly wants the commit-and-push workflow. Do not trigger implicitly for ordinary coding or review tasks.

Original author description

Explicitly run the repository push workflow on the development branch only: build, run tests, stage and read the change, write a conventional commit message, commit, then push the development branch. Use only when the user clearly wants the commit-and-push workflow. Do not trigger implicitly for ordinary coding or review tasks.

How it works

  1. Procedure
  2. Output
Original SKILL.md headings · 71 lines, 419 words
SKILL.md preview
---
name: push
description: >-
  Explicitly run the repository push workflow on the development branch only:
  build, run tests, stage and read the change, write a conventional commit
  message, commit, then push the development branch. Use only when the user
  clearly wants the commit-and-push workflow. Do not trigger implicitly for
  ordinary coding or review tasks.
disable-model-invocation: true
---

# Push Workflow

Execute this workflow only after the user explicitly asks for it. It pushes only the development branch. It never checks out, merges or pushes the release branch.

## Procedure

### Step 0: Confirm the branch

```sh
git branch --show-current
```

The branch must be the `developmentBranch` of `harness.config.json`. If it is anything else, stop and report it.

### Step 1: Build

Run `npm run build`. A `workstation:` failure is fixed on the machine by the remedy it names, then the build runs again (`AGENTS.md`, hard prohibitions). If the build fails otherwise, stop and report the failure.

### Step 2: Run tests

Run `npm test`. If tests fail, rerun each failed test in isolation. Stop only if an isolated rerun still fails.

### Step 3: Stage and read the change

```sh
git status --short --untracked-files=all
```

An empty status means there is nothing to commit: skip to Step 5, which pushes commits already made.

The commit takes every change the status lists, unless the user named a narrower scope. Stage with `git add .` or `git add -- <path>...`, then check what is staged, before anything prints its content:

```sh
git diff --staged --name-status
npm run --silent secrets:staged
```

The scan names a path and the kind of finding, never the value. If it refuses, stop and ask, leaving the index as it is, and do not open the paths it named. Once it passes, read the content:

```sh
git diff --staged
```

Stop and ask, leaving the index as it is, when the staged names include a path outside the scope or miss one inside it, or when the staged content carries what looks like a credential the scan missed. Do not change anything to make either condition pass.

### Step 4: Commit

Use a conventional commit message: `<type>(<scope>): <subject>`. Never pass `--no-verify`.

### Step 5: Push and verify

```sh
git log --oneline origin/<developmentBranch>..<developmentBranch>
```

These are the commits the push will send, with `<developmentBranch>` read from `harness.config.json`. If the list is empty, report `Nothing to push` and stop.

`<developmentBranch>` is the value from `harness.config.json`. Run these commands sequentially, never chained with `&&`:

```sh
git push origin <developmentBranch>
git status --short --branch --untracked-files=all
```

The final status shows the branch neither ahead of nor behind the remote. If it shows anything else, stop and report it. If any command fails, stop and report the error. Never force a push.

## Output

Report the final commit message, the commits sent, the push result and the final status.

Versions

RepositoryScoreLicence
This page · yesgenius/agent-harness95MIT
AsiaOstrich/universal-dev-standards100MIT
hamedmp/matrix-os100AGPL-3.0
AsiaOstrich/universal-dev-standards100MIT
AsiaOstrich/universal-dev-standards100MIT
JQ-WCoding/devkit100MIT
Mooshieblob1/MooshieUI100AGPL-3.0
AsiaOstrich/universal-dev-standards100MIT
tibursocampos/agent-dev-toolkit100MIT

Database snapshot: 13.11.2026 · package version 5499cdca02ce (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95commit
    Explicitly run the repository commit workflow: build, run tests, stage the change and read it, write a conventional commit message, then commit and stop. Nothing is pushed. Use only when the user clearly wants the work committed without a push. Do not trigger implicitly for…
  • 91commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 90commit-push-current
    Use when a human explicitly asks to commit and push to the checked-out branch with no branch creation and no pull request. Not for the default branch: use commit-push-main; not for a pull request: use commit-push-pr.
  • 90commit
    Stage, commit, and push changes to the current branch. Use when asked to commit, push, or create a commit for the current task.
  • 90gh-issue-fix-flow
    End-to-end GitHub issue fix workflow using gh, local code changes, builds/tests, and git push. Use when asked to take an issue number, inspect the issue via gh, implement a fix, run XcodeBuildMCP builds/tests, commit with a closing message, and push.
  • 100commit-push
    Commit changes and push to the current branch remote. Use when you want to commit local changes and push them upstream in one workflow, with branch protection against main/master.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.