Pushing CI Changes

by deonmenezes

Pushing CI Changes is a DevOps skill for Claude Code, published by deonmenezes in mantishack.

490 stars73 forkson deonmenezes/mantishackAdded 2026/08/26Repository updated 2026/08/11

View source on GitHub Download repo ZIP

agent-harnessai-agentsautonomous-agentsbug-bountyclaude-codemantismcpoffensive-securitysecurity

Install in seconds

Install Pushing CI Changes

Copy Pushing CI Changes into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/deonmenezes/mantishack/tree/main/.codex/skills/pushing-ci-changes ~/.claude/skills/pushing-ci-changes

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/deonmenezes/mantishack.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .codex/skills/pushing-ci-changes/SKILL.md in deonmenezes/mantishack
Installs to: ~/.claude/skills/pushing-ci-changes
Collection: One of 25 skills cataloged from this repository
Category: DevOps — 798 skills

What Pushing CI Changes does

Pushing CI Changes helps when updates to .github workflow files are rejected because approval is required. It tells you to request the temporary workflow access and retry after it propagates.

Pushing CI Changes is cataloged under DevOps on DirSkills. Pushing CI Changes comes from a repository tagged agent-harness, ai-agents, autonomous-agents, bug-bounty and claude-code.

Documentation

README

From the original repository

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.

Frequently asked about Pushing CI Changes

What else does deonmenezes publish alongside Pushing CI Changes?
Pushing CI Changes is one of 25 skills that DirSkills catalogs from deonmenezes/mantishack, the repository it ships in. Its siblings there include Canary Tripwire Response, Code Breaking Changes and Code Review. Each one is a separate skill with its own page in this directory, installs the same way Pushing CI Changes does, and is maintained by deonmenezes in that same repository. The rest of the collection is listed on the deonmenezes/mantishack page.
How does Pushing CI Changes compare to other DevOps skills?
Pushing CI Changes ranks #716 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Pushing CI Changes against them. Open each page to compare what they document and how they install.