Updated 3mo ago
by pimenov
codex-first-skills-pack
Публичный пакет инженерных skills для Codex
26 GitHub stars (26)
+1 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | +1 |
| Oct 15 | 0 |
| Oct 16 | 0 |
- 11 skills (11 skills found in its SKILL.md files)
- 4 forks (4 forks)
- 3mo ago last update (Last updated 3mo ago)
Install
Skills CLI
npx skills add pimenov/codex-first-skills-pack
Asks which skills and agents to install. Just one: npx skills add pimenov/codex-first-skills-pack --skill api-and-interface-design — add -g for every project.
Claude Code
git clone https://github.com/pimenov/codex-first-skills-packcp -r "codex-first-skills-pack/skills/api-and-interface-design" ~/.claude/skills/
Copies the api-and-interface-design skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add pimenov/codex-first-skills-pack
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
api-and-interface-design
Designs stable API, interface, schema, event, CLI, module, and service contracts before implementation so callers, consumers, and future agents can depend on them safely. Use when creating or changing public/internal APIs, SDK surfaces, webhooks, GraphQL/REST/RPC routes, database or message contracts, module boundaries, config formats, CLI commands, or any interface where compatibility, versionin…
skills/api-and-interface-design/SKILL.md on GitHub (opens in a new tab) -
code-review-and-quality
Reviews code changes across correctness, tests, readability, architecture, security, and performance before they are merged, shipped, or called done. Use when the user asks for a code review, when reviewing a PR/diff/commit/agent-produced code, after implementation or bugfix before final confidence, when deciding whether a change is ready, or when large/unclear changes need findings with severity…
skills/code-review-and-quality/SKILL.md on GitHub (opens in a new tab) -
context-engineering
Curates focused project and session context before answering, planning, editing, debugging, reviewing, deploying, or handing off work. Use when starting or resuming work in a repo/workspace, switching tasks, output quality degrades, the codebase is unfamiliar or large, source-of-truth is unclear, docs/code/runtime may conflict, or Codex needs a bounded context pack before taking action.
skills/context-engineering/SKILL.md on GitHub (opens in a new tab) -
debugging-and-error-recovery
Guides systematic root-cause debugging and recovery instead of guessing fixes. Use when tests fail, builds break, commands error, logs or consoles show errors, runtime behavior differs from expectation, a bug is reported, a prior fix did not work, CI/deploy/smoke checks fail, or something worked before and stopped working. Also use when Codex encounters an unexpected tool, package, API, network,…
skills/debugging-and-error-recovery/SKILL.md on GitHub (opens in a new tab) -
deprecation-and-migration
Plans safe deprecation, migration, sunset, replacement, and removal of old systems, APIs, features, schemas, flags, cron jobs, integrations, configs, libraries, UI flows, and operational processes. Use when retiring legacy code, replacing an implementation, removing a public/internal interface, migrating consumers, consolidating duplicate systems, deciding maintain-vs-sunset, writing deprecation…
skills/deprecation-and-migration/SKILL.md on GitHub (opens in a new tab) -
doubt-driven-review
Runs an adversarial review gate for non-trivial or high-stakes decisions before they stand. Use when Codex is about to claim something is safe, correct, reversible, production-ready, scalable, idempotent, secure, or compliant; when work touches production, auth, permissions, secrets, billing, public APIs, migrations, irreversible cleanup, customer data, external agent CLIs, or unfamiliar code wit…
skills/doubt-driven-review/SKILL.md on GitHub (opens in a new tab) -
incremental-implementation
Breaks large or multi-file implementation work into small verified slices that keep the project working after each step. Use when building a feature, bugfix, refactor, migration, integration, UI flow, or operational change that could become a large diff; when more than one file/module is touched; when scope is fuzzy; when review or rollback would be hard; when Codex is tempted to code for a long…
skills/incremental-implementation/SKILL.md on GitHub (opens in a new tab) -
planning-and-task-breakdown
Turns ambiguous, large, multi-step, or handoff-prone work into sequenced tasks with outcomes, dependencies, stop-lines, acceptance criteria, and the right durable layer. Use when planning a feature, bugfix campaign, refactor, migration, deploy prep, client/internal work packet, Linear issue set, or when the user asks to break down, plan, scope, make tasks, prepare execution, or decide the next sa…
skills/planning-and-task-breakdown/SKILL.md on GitHub (opens in a new tab) -
source-driven-development
Grounds framework, library, SDK, API, CLI, and cloud-service implementation decisions in current official sources before code or recommendations. Use when building, debugging, reviewing, or explaining version-sensitive technical work; when the user asks for latest/current/correct/documented behavior, актуальные docs, current docs, official docs, or как сейчас правильно; when a dependency, SDK, pr…
skills/source-driven-development/SKILL.md on GitHub (opens in a new tab) -
spec-driven-development
Defines the implementation contract before planning or coding so work is built against explicit goals, users, scope, non-goals, assumptions, acceptance criteria, and verification. Use when creating or changing a feature, product workflow, API, integration, migration, user-facing behavior, cross-team handoff, or any task where Codex could implement the wrong thing correctly; when the user asks for…
skills/spec-driven-development/SKILL.md on GitHub (opens in a new tab) -
test-driven-development
Drives behavior changes through tests or explicit focused checks before implementation. Use when implementing new logic, fixing a bug, changing behavior, adding edge-case handling, modifying validation, refactoring behavior-sensitive code, or after debugging identifies a root cause that needs a regression guard. Also use when Codex is about to say a bug is fixed or behavior works but no proof exi…
skills/test-driven-development/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.