15,311 mods in this category, of every kind an agent can take. Each one carries what it costs per session, what the scan found, and whether it is the original.
Skill Claude CodeCodex
PRD-driven delivery loop with a token-lean audit trail (requests → decisions → specs → tasks → commits). All docs/ log access goes through ./scripts/owl. Use for any feature, bug fix, or change in a repo using ATHENA docs/.
Skill Claude CodeCodex
Use Jujutsu (jj) for version control in jj-enabled projects. Covers command workflows, bookmark management, rebasing, conflict resolution, revsets, and common pitfalls. Triggers when: project has a .jj/ directory, README requires jj, or user explicitly requests jj commands. Do NOT use for regular git-only projects.
Command Claude Code
Iteration delivery — delivery check + archive + commit & tag + bump version.
Soul-Brews-Studio/plugin-marketplace
Command Claude Code
Find projects across git history, repos, docs, and Oracle. Use when user asks "trace", "find project", "where is [project]", "search history". Supports --oracle (fast), --deep (5 subagents), and trace logging.
Skill Claude Code
Ingests open retro issues, investigates via scramstorm, dispatches scram team to address changes, bumps version, comments on issues, commits and pushes.
Skill Claude CodeCodex
Upload images to img402.dev for embedding in GitHub PRs, issues, and comments. Images 1MB or under are free AND permanent — no payment, no auth — which covers virtually every screenshot. Larger images (up to 10MB) are free for 30 days, or permanent for $0.01 USDC via x402. Use when the agent needs to share an image in…
Skill Claude Code
Structured git workflow with Conventional Commits standard. Covers commit formatting, PR creation via gh CLI, merge conflict resolution, advanced git operations (cherry-pick, bisect, worktrees), repository archaeology, and branch cleanup.
Skill Claude CodeCodex needs its repo
A software-development workflow that turns a written request into a specification, an execution plan, code changes, tests, and commits. A specification describes what should be built; a plan describes how.
Skill Claude CodeCodex
Bootstrap an app-agnostic set of deploy scripts into an Expo React Native + web project and run the full lifecycle of publishing a mobile app to both the Apple App Store (TestFlight) and Google Play, plus store-screenshot capture.
Skill Claude CodeCodex
A workflow for completing development tasks in projects that use BossCoding, a project process with repository rules, checks, branches, pull requests, and continuous integration.
Plugin Claude Code
Bundles 2 skills, 2 commands · 80 tokens together
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
Skill Claude CodeCodex
A reusable instruction set for producing a Git branch name, commit message, and GitHub pull request text from one set of branch changes.
Skill Codex
Git-backed memory policy and CLI workflow for OpenClaw, Hermes, Claude Code, Codex, and other agents. Use when an agent should remember durable user preferences, project decisions, conventions, lessons learned, or query/audit Git-native memory with gam.
Denis-Ibraliu/commonkit-skills
Plugin Claude Code
Bundles 5 skills · 373 tokens together
A light engineering workflow kit: brainstorm a spec, implement it, review once at the end, and ship the full git lifecycle.
Skill Claude Code
This skill should be used when the user asks to "autofix pr", "fix pr locally", "fix ci failures", "fix review comments", "iterate on pr", "fix failing checks", "fix pr comments", "make ci green", "fix the build", "address reviewer feedback", or wants to iteratively fix CI failures and review comments on a GitHub PR…
lifeinchords/claude-code-skills
Skill Claude Code
Share reusable agentic patterns from project repos back into an upstream template, safely. WHEN TO PROPOSE: (1) After pushing commits touching high-signal paths, (2) Sprint/milestone review, (3) When agentic tooling is created. Classify commits as: YES (portable), MAYBE (needs changes/judgment—offer to fix), or NO…
Skill Claude CodeCodex
Write features, fix bugs, and create PRs for the NanoClawbster codebase. Works in an isolated dev workspace, pushes via Composio (CI validates on GitHub Actions), and deploys after user approval.
Skill Claude Code
Drive a task queue (loop-tasks.md) to completion in ANY repo. Detect the repo's own rules, then for each task a check-writer writes hidden acceptance checks, then plan -> /review-plan -> implement -> verify -> /review -> fix all findings -> /battle-test -> gate (the checks decide) -> commit -> push -> client doc ->…
Skill Claude CodeCodex
Deep review of all changes on the current branch using scaled finder agents with deduplication, falsification, and intent verification.
Skill Claude Code
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.
SaharCarmel/Sahar-claude-code-marketplace
Skill Claude CodeCodex
This skill should be used when the user asks to "create a PR", "open a pull request", "submit my changes", "push and create PR", "finalize my work", "/pr", or wants to commit, validate, and push their current branch as a pull request. Handles the full workflow: commit all changes, run quality gates with best-effort…
Command Claude Code
Command "code-review" from r0r1/claude_code_config, covering review github pr with linear issue specification, arguments provided, prerequisites check, step 1: extract github repository and pr information and step 2: fetch linear issue details.
Skill Claude Code
Wrap up a coding session — update docs, lint, then commit. Use when the user says "done", "wrap up", or "finish".
Skill Claude Code
Commit current changes to git with concise messages. Use whenever the user says "commit", "save changes", or asks to commit their work.
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: