openclicky-repo-operator

Manage Git repositories, GitHub pull requests, code reviews, and CI debugging workflows.

Updated Jul 7, 2026

Search Tags:#git #code review #pull request #commit #github #github actions #ci debugging

Ready to run

npx skills add https://github.com/jamsdoescode/Erik-s-Portfolio --skill openclicky-repo-operator-jamsdoescode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclicky-repo-operator
Source: https://github.com/jamsdoescode/Erik-s-Portfolio/tree/main/openclicky/AppResources/OpenClicky/OpenClickyBundledSkills/openclicky-repo-operator
Command: npx skills add https://github.com/jamsdoescode/Erik-s-Portfolio --skill openclicky-repo-operator-jamsdoescode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Git and GitHub involves many confusing states—dirty working trees, unpushed commits, failing CI checks, and unclear review feedback. This Skill acts as a repo operator that inspects your local checkout, explains Git state in plain language, and performs commits, pushes, PRs, and CI debugging safely. ## Core Features & Use Cases - Repository Orientation: Inspect branches, remotes, dirty state, and codebase structure to explain what is saved, pushed, or pending. - Git Workflow Execution: Create branches, stage, commit, push, and open pull requests using local git, the GitHub CLI, or Composio GitHub tools. - Review & CI Support: Review diffs, respond to review comments, and diagnose GitHub Actions failures with concrete next steps. - Use Case: You fixed a bug locally but are unsure whether it is pushed. The Skill checks your branch and remote, summarizes the changed files, commits with your approval, pushes, and opens a PR with the URL. ## Quick Start Ask the assistant to check the current repo status, commit the pending changes on a new branch, and open a pull request on GitHub.

Frequently Asked Questions about openclicky-repo-operator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a branch, commit changes, and open a GitHub pull request?▼

The Skill checks your current branch and dirty state with local git, summarizes the files to be included, then commits and pushes only after your confirmation. It opens the pull request through the GitHub CLI or Composio GitHub tools and reports the PR URL.

How can I debug a failing GitHub Actions workflow?▼

The Skill classifies the task as a CI fix, then pulls Actions logs through the GitHub connector or gh CLI to identify failing checks. It reports the failing files and next action, and tells you exactly which permission or auth is missing if logs are unavailable.

Can it explain whether my local changes are saved or pushed to GitHub?▼

Yes. It inspects the local checkout's branch, remote, and dirty state, then explains in plain language what is committed, what is unpushed, and what is still uncommitted. This is designed for users confused by GitHub Desktop or local folder state.

What happens if the GitHub integration or gh CLI is not authenticated?▼

The Skill stops and reports the exact missing setup step, such as authentication or permissions, instead of looping or silently switching to browser automation. It falls back from Composio GitHub tools to gh when gh is authenticated.

Will it ever discard my changes or force-push without permission?▼

No. The Skill never discards user changes without explicit instruction and never force-pushes unless you explicitly ask and understand the risk. Before any commit, push, or PR, it summarizes exactly which files are included.

When should I not use a repo operator skill?▼

Avoid it for building a new visible website or app from scratch, pure local dev environment or API key setup without repo work, or simply opening a generated code artifact. Those cases belong to dedicated build-preview, dev-setup, or artifact skills.