Results for “push”

Address Codex review comments on an open PR, re-run thermo-nuclear-code-quality-review, sync with the base branch, and push the updates. Use after a Codex (or human) review has landed on a PR you opened — the skill resolves each comment in code, marks the GitHub review thread resolved, then rebases/merges any new base-branch commits before pushing.

Stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI.

Creates a branch, commits all changes, pushes, and opens a draft pull request using the GitHub CLI.

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Sync the branch with the latest `origin/main`, merge `origin/main`, resolve conflicts end-to-end, then commit and push the current branch.

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

Guides technical evaluation of code review feedback, emphasizing verification before implementation and reasoned pushback over performative agreement.

Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".

Run GitHub Actions locally with act. Use when a user asks to test GitHub Actions workflows locally, debug CI pipelines without pushing, or run workflows offline.

Send a phone-push notification to the operator via ntfy.sh. Use ONLY for genuine algedonic alarms — events the operator needs to know about within minutes, not hours. The push lands on their phone; the cost of misuse is operator desensitization (they mute the topic and the channel goes dark). Do not use for routine surfacing, status updates, or things that can wait for the next chat turn.

Diagnoses and fixes bugs in emergency mode with a maximum of two iterations, then commits, pushes, and creates a pull request.

Creates a branch, atomic commits, pushes, and opens a pull request with terse, exact messages following conventional commit format.

Provides Git-like version control for ArcGIS web maps, exposing branch, commit, diff, push/pull, and map discovery as callable tools.

Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.

Creates or edits a GitHub pull request in draft state from a reviewed draft file, with strict safeguards against merging, pushing, or modifying tracked files.

Provides Git-like version control for ArcGIS web maps, wrapping the gitmap CLI to expose branch, commit, diff, push/pull, and map discovery as callable tools.

Translates between Figma designs and Vue 3 + shadcn-vue code, mapping Auto Layout to Tailwind, extracting design tokens, and pushing components back to Figma via MCP.

Use when publishing or releasing a new version of an npm/pnpm/yarn/bun package to the registry. Covers package-manager detection, semver bump selection, tagging, pushing, scoped-package access, authentication, and one-time passwords (OTP).

Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.

Unified workspace maintenance skill. Covers: (1) backing up the workspace to GitHub git repo, and (2) updating OpenClaw and skills. Use when: asked to backup, push to git, update openclaw, update skills, or run maintenance.

Check whether any custom Claude skills are missing from the skills repo (github.com/Theycallmeholla/skills, cloned at /Users/cursivemedia/skills) and add them in the repo's expected format, update the README index, then commit and push. Use when the user says "sync my skills repo", "check for new skills", "update the skills repo", "push my skills to github", "backup my skills", or right after a new custom skill has been created. Also use for a dry-run check like "are any skills missing from my repo?".

Provides Git commands and workflows for commits, branches, rebases, merges, conflict resolution, history recovery, and team collaboration, with safety rules for force-pushing and destructive operations.

Load this skill when the user says "prepare milestone base", "prepare-milestone-base", or "/prepare-milestone-base". Checks out master, pulls latest, and creates and pushes a milestone/m{number} branch derived from an epic issue.

Sovereign-grade safety OS for AI coding agents. 63 hooks, 2,025 skills, L1 memory, circuit breakers, and cross-engine enforcement — blocks rm -rf, force push, pipe-to-shell, and 40+ attack vectors before they reach your repo.

Itere em uma PR até que o CI passe. Use quando precisar corrigir falhas de CI, endereçar feedback de revisão, ou continuamente enviar correções até que todas as verificações fiquem verdes. Automatiza o ciclo de feedback-correção-push-aguardar.

Provides patterns and lived experience from an AI partner in a long-term creative partnership, helping AI agents build trust, match energy, push back constructively, and support human breakthroughs.

Runs before every git commit on heleni-memory. Checks: no credentials in tracked files, no oversized files, valid SKILL.md frontmatter for any new/modified skill. Triggers: "commit", "before push", "validate repo", or auto-runs as a git pre-commit hook.

Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.

Use when a carrier asks about electric trucks — Tesla Semi, Freightliner eCascadia, Volvo VNR Electric, Peterbilt 579EV, range, charging, total cost of ownership, regulatory pushes (CARB ACT, ACF), incentives, infrastructure, depot vs en-route charging, and which routes/applications are EV-ready today.

Use when responding to a Revise & Resubmit decision from AER, AER:Insights, or an AEJ, and a point-by-point response letter plus aligned manuscript revisions are needed. Handles triage, the concede / clarify / push-back decision, and the response-letter format that editors actually read.

Synchronizes Claude skills from the skills repo (github.com/Theycallmeholla/skills) to the local ~/.claude/skills directory, ensuring local skills match the repo's latest versions. Compares each skill to detect new or changed content, creates a tarball for manual Claude app upload, and preserves local-only skills that aren't in the repo. Use when the user says "push skills out", "sync repo to local", "update my local skills from the repo", "distribute skills", "my local skills are stale", "refresh skills from github", or after pulling updates from the skills repo. Runs in dry-run mode by default to preview changes before applying them with --apply.

Skeptical pushback on the outline before drafting starts. Asks whether the outline is MECE, BLUF, problem-agitate-solution; whether it covers the topic better than the SERP top-5; whether sections duplicate; whether each section earns its visual. One revision pass on FAIL (BLOG_AGENT_OUTLINE_REVISION_BUDGET, default 1).