izyanrajwani/agent-skills-library

🛠️ Enhance programming workflows with a curated library of agent skills for tasks like code review, debugging, and planning for efficient project execution.

4Stars on the repository
14Mods indexed here, across every type
2d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

brainstorming

01

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Collaborative design exploration that refines ideas into validated specs through iterative questioning. Use before any creative work including creating features, building components, adding functionality, or modifying behavior.

not rated 4 2d ago A 38 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.

not rated 4 2d ago A 53 tokens

executing-plans

03

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.

not rated 4 2d ago A 32 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Assesses and responds to incoming code review feedback on PRs (reviewer comments, requested changes), especially when suggestions are unclear, technically questionable, or scope-expanding. Use before implementing review suggestions to align on intent and keep changes minimal.

not rated 4 2d ago A 53 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Use when you need to request a code review for a PR/MR and want a consistent review brief (context, scope, risk areas, test instructions, acceptance criteria) before merge.

not rated 4 2d ago A 42 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Sequential subagent execution with two-stage review gates for implementation plans. Use when executing multi-task plans in current session, when tasks need fresh subagent context to avoid pollution, when formal review cycles (spec compliance then code quality) are required between tasks, or when you need diff-based…

not rated 4 2d ago A 68 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.

not rated 4 2d ago A 35 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.

not rated 4 2d ago A 37 tokens

using-git-worktrees

10

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Git worktree–based workspace isolation for parallel or non-disruptive development. Use when work must occur without modifying or interfering with the current working tree.

not rated 4 2d ago A 37 tokens

using-superpowers

11

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Meta-skill enforcing skill discovery and invocation discipline through mandatory workflows. Use when starting any conversation to check for relevant skills before any response, ensuring skill-first workflow before proceeding.

not rated 4 2d ago A 38 tokens

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.

not rated 4 2d ago A 41 tokens

writing-plans

13

izyanrajwani/agent-skills-library

Skill Claude CodeCodex

Structured implementation planning for multi-step development tasks. Use when you have a spec or requirements and need to break work into executable steps.

not rated 4 2d ago A 30 tokens

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: