Agent skill

Pushing CI Changes

by deonmenezes in deonmenezes/mantishack

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

Apache-2.0Auto-check passedDevOps & Cloud

Install Pushing CI Changes

skills CLI
$ npx skills add deonmenezes/mantishack --skill pushing-ci-changes -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install deonmenezes/mantishack pushing-ci-changes --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/deonmenezes/mantishack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/pushing-ci-changes .claude/skills/pushing-ci-changes && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pushing-ci-changes
GitHub stars
504
Token cost
~224 tokens
SKILL.md length
122 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

  • Tasks that involve CI/CD
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pushing CI Changes is an agent skill from deonmenezes/mantishack. Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

Its SKILL.md is about 220 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve CI/CD

Example prompts

  • “/pushing-ci-changes”

What it can do on your machine

Read from SKILL.md and the folder at commit c3a2e68. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pushing CI Changes loads about 224 tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 122 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~224

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from deonmenezes/mantishack at commit c3a2e68, republished under its Apache-2.0 licence (© deonmenezes). 122 words, ~224 tokens.

Download SKILL.mdSave it as .claude/skills/pushing-ci-changes/SKILL.md (or your agent's skills folder).
name
pushing-ci-changes
description
Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

The Codex repository prevents anyone from uploading changes to its CI configuration unless they've been granted a temporary role.

In order to push changes to .github/**/*.yml and related files you'll need the user to read go/workflow-approvals and request an approval through that flow. It is not possible for you to make progress by requesting an exemption yourself.

If you know you're about to push changes that would fail due to these restrictions you should still try to push anyways to confirm the user's account doesn't already have the necessary approval.

If you encounter a failed push due to these restrictions, share the go/workflow-approvals link with the user and ask them to return control to you once the approval has propagated to GitHub.

© deonmenezes, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/pushing-ci-changes of deonmenezes/mantishack.

Open the folder on GitHubat commit c3a2e68

Compare with similar skills

Pushing CI Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pushing CI Changes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pushing CI Changes this skilldeonmenezes/mantishack504—~224Automated safety check: PassApache-2.0
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
GitHub Actions Templatesbartstc/vite-ts-react-template12214 repos~1.9kAutomated safety check: PassMIT
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
Repo Hygiene Scan and FixQwenLM/qwen-code28k—~1.7kAutomated safety check: PassApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence

Similar skills

  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • GitHub Actions Templates

    bartstc/vite-ts-react-template

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.

    122 GitHub starsUsed in 14 repos~1.9k tokens
    DevOps & CloudAuto-check passed
  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.

    28k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

More from deonmenezes/mantishack

All 11 skills in this repo
  • Codex Issue Digest

    deonmenezes/mantishack

    Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows.

    504 GitHub stars~2.3k tokensUpdated 6 days ago
    Auto-check passed
  • Codex Bug

    deonmenezes/mantishack

    Diagnose GitHub bug reports in openai/codex. An agent skill from deonmenezes/mantishack.

    504 GitHub stars~643 tokensUpdated 6 days ago
    Auto-check passed
  • Detection Breadth

    deonmenezes/mantishack

    When and how to reach for the companion detectors -- bandit (Python SAST) and trivy (deps + secrets + IaC misconfig) -- alongside the core semgrep/CodeQL/osv/trufflehog toolchain

    504 GitHub stars~510 tokensUpdated 6 days ago
    Auto-check passed
  • HTTP Evidence

    deonmenezes/mantishack

    Turn a captured HTTP request/response into a bounded, redacted evidence pack with a stable request-ref using the mantishttpaudit MCP server, instead of pasting raw traffic into a finding

    504 GitHub stars~455 tokensUpdated 6 days ago
    Auto-check passed
  • Program Analysis

    deonmenezes/mantishack

    Use astgrepscan, sourcesinkscan, and smtcheckreachability (mantisprogramanalysis MCP server) to move a candidate toward a proven-reachable finding

    504 GitHub stars~551 tokensUpdated 6 days ago
    Auto-check passed
  • Canary Tripwire Response

    deonmenezes/mantishack

    What to do if a mantiscanary decoy tool ever shows up as tempting or gets called -- treat it as a security incident, not a normal tool result

    504 GitHub stars~376 tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Pushing CI Changes

What does Pushing CI Changes do?

Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions. Pushing CI Changes is an agent skill from deonmenezes/mantishack. Pushing GitHub Actions changes, resolving push rejection, requesting upload exceptions.

When should I use Pushing CI Changes?

Pushing CI Changes fits situations like: tasks that involve CI/CD.

How do I install Pushing CI Changes in Claude Code?

Run `npx skills add deonmenezes/mantishack --skill pushing-ci-changes -a claude-code`. Or copy the skill folder (.codex/skills/pushing-ci-changes in deonmenezes/mantishack) into .claude/skills/pushing-ci-changes in your project. Claude Code loads it when a task matches its description.

How do I install Pushing CI Changes in Codex?

Run `npx skills add deonmenezes/mantishack --skill pushing-ci-changes -a codex`. Or copy the skill folder (.codex/skills/pushing-ci-changes in deonmenezes/mantishack) into .agents/skills/pushing-ci-changes in your project. Codex loads it when a task matches its description.

Can I use Pushing CI Changes in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deonmenezes/mantishack --skill pushing-ci-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pushing-ci-changes, .gemini/skills/pushing-ci-changes, .github/skills/pushing-ci-changes and .opencode/skills/pushing-ci-changes in your project.

What does Pushing CI Changes need to run?

SKILL.md names no scripts, command-line tools or credentials: Pushing CI Changes is instructions for the agent only.

Does Pushing CI Changes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pushing CI Changes safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pushing CI Changes use?

Pushing CI Changes is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pushing CI Changes use?

About 224 tokens (SKILL.md is roughly 896 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pushing CI Changes?

Skills that share tags, products or a category with Pushing CI Changes: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pushing CI Changes?

deonmenezes (a GitHub user) maintains it in deonmenezes/mantishack, which has 504 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.

Source: deonmenezes/mantishack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.