Skill Codex
A workflow for creating a ZIP archive containing only Git-untracked files. Untracked files are new files Git is not yet tracking.
9,850 tagged Git and workflow, measured the same way as everything else here.
Browse within: LLM 191cli 161agents 135agentic-ai 100agent 89skills 85ai-coding 84javascript 60cursor 58agent-orchestration 49agent-framework 48Autonomous Agents 41context-engineering 37coding-agent 35
Skill Codex
A workflow for creating a ZIP archive containing only Git-untracked files. Untracked files are new files Git is not yet tracking.
Skill Claude CodeCodex
A guide to Git worktrees, which let one Git repository have several working directories at the same time.
Skill Claude CodeCodex
Open a GitHub pull request using the kit PR template. Use when the user asks to open/create a PR, push and PR, or publish a branch. Write a detailed, product-facing description. Contracts and harness review stay local — never put feature IDs, contract paths, or harness sections in the PR title or body.
Skill Claude CodeCodex
Reference for interacting with GitHub (gh CLI), and the Atlassian stack — Jira, Confluence, Bitbucket, JSM — via atlassian-cli. Use when reading/writing issues, PRs, pages, or comments in any of these tools.
Skill Claude CodeCodex
Reimplement a messy git branch with clean, narrative-quality commit history suitable for code review. Use when a branch has WIP commits, debug commits, or trial-and-error history that needs to be transformed into a reviewable story before creating a PR.
Skill Claude CodeCodex needs its repo
Bootstrap a new repo into Katala OS agent-context style — AGENTS.md inheriting the global baseline, cross-OS .gitattributes, shared pre-commit hook via core.hooksPath, optional hash-locked CONSTITUTION + manifest.lock.json + verify.sh, NEEDSREVIEW.md. Use when the operator asks to "start a new repo", "scaffold an…
Skill Claude CodeCodex
Push committed work, open a PR against dev, and land it with a merge commit so no commit is ever rewritten or duplicated. Use when invoked as /iso-push [--pr] [--cascade test|prod] [--no-merge] [--stay], or when asked to push a branch, open a PR against dev, or promote dev to test or prod. Requires a dev or develop…
Skill Codex
Use when a Codex repository relies on OpenSpec proposals and the work is moving from approved change to implementation in an isolated git worktree. Covers bootstrapping repositories with owf init, inspecting lifecycle state, starting implementation worktrees, applying migration rules, and cleaning up after merge. Do…
Skill Codex
Terminal-friendly BEFORE/AFTER recap for a PR or a commit — what was done, what was found, what's left.
Skill Claude Code
Create well-formatted git commits with conventional commit messages.
herakles-dev/opensource-pipeline
Skill Claude CodeCodex
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'.
chentao326/codex-claude-handoff
Skill Codex
A file-based handoff process between Codex and Claude Code. It moves work through six phases—specification, planning, building, review, polishing, and committing—using signal files to show which phase is current.
Skill Claude Code
A repository setup skill that adds a reusable structure for working with coding agents, including instructions, skills, hooks, shared session state, and code checks.
Skill Claude CodeCodex
Address PR review comments — analyze, fix, push, and reply.
Skill Claude CodeCodex
Review pending git changes and create senior-quality commits. Groups unrelated changes into separate logical commits, writes Conventional Commits messages that explain the why, and executes them — all on a tight token budget. Use when the user says "commit", "commit my changes", "commit like a pro", "ship this", or…
Skill Claude CodeCodex
ZOEHIS Git delivery: commit, push, merge to release branches, cherry-pick, create tags. Use when committing code to master, pushing to remote, merging from master to release-1.166/1.168 branches, cherry-picking specific commits, tagging releases, or handling system parameter (jsonl) separate commits. Also manages the…
Skill Claude CodeCodex
Apply Lytos Git conventions — branch naming, commit message format, merge workflow, and collaboration rules. Use when creating a branch, committing changes, opening a PR, or resolving a workflow conflict or question.
Skill Claude CodeCodex
Create a GitLab Merge Request — clear title, high-level summary of what was changed and why, explicit confirmation the issue is resolved, then a brief key-result comment on the issue.
Skill Claude Code
Inspect git history and append work summary to the daily work log.
luckyangf/repo-memory-workflow
Skill Claude CodeCodex
Guides users through repo-memory-workflow setup, task splitting, checkpointed AI development, and codex exec relay loops. Use when the project has AGENTS.md and .ai/TASK.md, or when the user says install this, initialize test, run a loop test, loop stuck, Round 1 starting, init, setup, Missing runloop, continue task…
Skill Claude Code
Declare and manage MergeChain PR merge-dependencies from the terminal or AI agent. Use when marking a PR blocked by another, setting up stacked-PR dependencies, or during push/open-PR flows for branches based on non-default bases (auto-detect prerequisite). Writes the visible managed PR-body section and exact hidden…
Skill Claude CodeCodex needs its repo
Format changelog content according to Replit's changelog template structure. Use when converting raw changelog content into properly structured documentation with correct frontmatter, sections, and media formatting.
Skill Claude CodeCodex
Writes clear, conventional-commit-style commit messages from staged git diffs, and can split unrelated changes into separate commits.
Skill Claude Code
Decide whether unreleased develop work warrants a release, pick the version per semver.org, and cut it following this repo's established commit/PR/tag/release pattern.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: