コレクション codex

Codex向けワークフロースキル＆開発連携 | AI Agent Skills

Claude Code・Cursor・Windsurf 向けの codex integrations AI Agent Skills 集合。開発者ワークフロー自動化を重視します。

Codex/OpenAI利用者向けに、一般的なツール羅列ではなく、再現性のある開発ワークフローに重点を置いたコレクションです。レビューサイクル、品質ゲート、デリバリー運用に使える再利用スキルと連携可能コンポーネントを収録。必要に応じてMCP対応も含みますが、主軸は実務的なコーディング運用です。

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from Codex workflow discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against Codex workflow fit, installation clarity, operator handoff, and day-to-day coding usefulness. This page is now positioned as an install-first Codex entry point instead of a generic integrations list.

We prioritize this page because users searching for Codex tooling usually need a shortlist they can install, validate, and carry into real coding workflows quickly.

Trust Signals

- Entries are chosen for practical Codex workflow value such as review loops, guardrails, handoff, and CLI-native execution.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable developer operations, not abstract brand adjacency or generic repository popularity.

Grouping Logic

- Lead with tools that can enter a Codex-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering review, handoff, automation, and workflow scaffolding.
- Use installation as the bridge from Codex discovery into validated daily execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or Codex workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one Codex workflow companion first

Use this page when you want one Codex companion that can enter real coding work without turning evaluation into another endless tooling loop.

1. Open the installation docs before opening more Codex-related repositories.
2. Choose one tool that best supports review, handoff, automation, or terminal execution.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider team workflow.

Add guardrails around a Codex coding loop

Treat the collection as an editorial filter when you need Codex-adjacent tools that improve coding quality without overcomplicating the stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more projects or more teammates.
4. Document the chosen Codex workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check Codex workflow choices before you standardize a team stack.

ai-development-guide

shinpr

Detects code smells, anti-patterns, and debugging issues. Use when: fixing bugs, reviewing code quality, or refactoring.

★ 34

⑂ 0

生産性

documentation-criteria

shinpr

Guides PRD, ADR, Design Doc, and Work Plan creation. Use when: planning features, writing specs, or creating technical documents.

★ 35

⑂ 0

生産性

testing

shinpr

Applies TDD process, test quality criteria, and mock guidelines. Use when: writing unit tests, using mocks, or reviewing test quality.

★ 0

⑂ 0

開発者

sync-readme

lbb00

sync-readmeはREADME.mdとREADME_ZH.mdを同期するためのツールです

★ 17

⑂ 0

update-docs

lbb00

Update all project documentation after code changes.

★ 17

⑂ 0

agent-gossip-coordinator

ruvnet

Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator

★ 16.7k

⑂ 0

review-design

janekbaraniewski

Review a design doc against the codebase

★ 8

⑂ 0

Related Authority Collections

If This Page Is Close, Keep Narrowing With Adjacent Authority Pages

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

P0 collection

Official AI Skills & Trusted Tools

A high-trust collection that lets the site lead with official and strongly verified ecosystems instead of random long-tail repos.

Trusted-brand collections are the fastest way to rebuild authority after pruning.

P0 collection

Agent Workflow Building Tools

A workflow-first collection that explains why related skills belong together and what job they solve.

Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.

P1 collection

Top Claude Code Skills

A platform-specific collection for one of the clearest demand clusters in the product ecosystem.

Platform collections let the site recover with narrower, more trustworthy topical intent.

P1 collection

Cursor-Compatible Skills

A clean surface for editor-specific demand with explicit workflow intent.

Editor-specific demand should land on curated surfaces, not random repo coverage.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

これらのコレクションはどのワークフロー向けですか？

ワークフロー自動化、プロセス自動化、ドキュメント操作、データワークフロー、再利用可能なスキルスタックを中心に構成されています。

コレクションとメインスキルディレクトリの違いは？

スキルディレクトリは直接検索やフィルタリングに適し、コレクションは完全なワークフロー向けの補完的スキルをまとめて見つけるのに適しています。

これらのコレクションをClaude CodeやCursorにインストールできますか？

はい。コレクション内のスキルは通常、Claude Code、Cursor、Windsurf、その他の対応環境で統一インストールフローにより動作します。

Additional Recovery Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

P0 collection

Agent Workflow Building Tools

A workflow-first collection that explains why related skills belong together and what job they solve.

Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.

P2 comparison

Claude Code vs Cursor vs Windsurf

Comparison pages are one of the best ways to prove independent judgment and avoid the mirror-site posture.

Comparisons make Killer-Skills look editorial-first instead of repo-wrapper-first.