codex-next

Plugin codex-next from marketplace codex-is-all-you-need in BlueSkyXN/Codex-is-all-you-need. Commands read from the repo's manifest — today.

Skills (60)

• core-codex-agents-md-builder

  为 Codex 仓库设计、审计或重构 AGENTS.md 层级；用于写/改/审计 AGENTS.md，不用于 CLAUDE.md 或 Cursor 规则。

• core-explore-unknowns

  Use only when the user explicitly invokes this skill to map unresolved product, domain, repository, or delivery unknowns before choosing a path.

• core-goal-run

  Use only when the user explicitly invokes this skill to create or resume a persistent file-based goal tracker across sessions.

• core-grilling

  Use only when the user explicitly invokes this skill to stress-test an existing plan or design through one load-bearing question at a time.

• core-router

  Use when the user asks how to use Codex Next, which bundled skill fits, or whether a workflow is needed. Do not trigger for a clear task that can be completed directly.

• core-skill-eval

  Use only when the user explicitly invokes this skill to evaluate a skill with representative cases, isolated runs, independent judging, and evidence-driven edits.

• data-analysis-report

  Use when converting data analysis results into a clear report with assumptions, findings, validation, limitations, and next steps.

• data-cleaning

  Use when planning safe data cleaning, deduplication, missing-value handling, anomaly handling, and reproducible cleaned outputs.

• data-sql-analysis

  Use when reviewing or creating SQL for analysis, metric definitions, joins, filters, aggregation, and validation queries.

• data-tabular-analysis

  Use when analyzing CSV, Excel, parquet, or table-like files and producing reproducible summaries.

• dev-accessibility-audit

  Use to audit web/app accessibility, including semantics, keyboard flow, focus, labels, ARIA, contrast, and responsive behavior.

• dev-api-contract-review

  Use to design or review API contracts, auth, pagination, versioning, errors, compatibility, and OpenAPI/GraphQL shape.

• dev-bugfix

  Use for a concrete defect or regression that needs reproduction, root-cause diagnosis, a fix, and regression validation. Do not trigger for routine localized edits or primarily performance-focused work.

• dev-build-optimization

  Use to diagnose or improve build speed, cache behavior, bundle size, packaging output, and monorepo task execution.

• dev-cli-auth-diagnosis

  Use when gh, hf, lark-cli, Git/SSH, or another authenticated CLI works in one shell or host but reports missing credentials, cannot refresh or persist authentication, cannot reach its service, or behaves differently inside Codex or across permission profiles, macOS, Windows, WSL, containers, or CI.

• dev-cli-tooling-workflow

  Use to design, implement, review, or test CLI tools, flags, config precedence, terminal UX, errors, and docs.

• dev-dependency-upgrade

  Use for dependency upgrades, vulnerability fixes, version conflicts, lockfiles, package managers, and migration risk.

• dev-frontend-ui-implementation

  Use to implement/review frontend UI, routing, state, API integration, responsive layout, accessibility, and browser behavior.

• dev-fullstack-feature

  Use when the requested feature genuinely spans at least two delivery layers such as frontend, backend, API, data, scripts, or tests. Do not expand a single-layer change into a full-stack workflow.

• dev-git-workflow

  Use for non-trivial Git state such as branch strategy, worktrees, merge/rebase decisions, conflicts, reviewer-facing PR preparation, tags, and release notes. Do not trigger for a routine commit, push, or PR that needs no strategy decision.

• dev-migration-plan

  Use to plan modernization, framework upgrades, service extraction, schema migrations, rewrites, and rollback paths.

• dev-performance-diagnosis

  Use for diagnosing slow code, APIs, queries, memory growth, frontend load, build regressions, resource bottlenecks, and scalability limits.

• dev-pr-review

  Use for reviewing a branch, pull request, local diff, or implementation plan before merge, including alignment of existing PR metadata with the diff and delivery state.

• dev-prompt-evaluation

  Use to design, test, compare, version, and validate prompts or LLM behavior with measurable criteria and datasets.

• dev-python-quality

  Use when Python-specific typing, async behavior, packaging, pytest, ruff/mypy, scripting, or performance quality is central to the request. Do not trigger for generic small code edits merely written in Python.

• dev-refactor-plan

  Use when the user asks for a behavior-preserving refactor plan before implementation. Do not trigger when the user already requested a clear, scoped refactor to be implemented directly.

• dev-release-check

  Use for pre-release validation, versioning, changelogs, artifacts, smoke tests, rollback notes, and release risk.

• dev-repo-onboarding

  Use to map an unfamiliar repo structure, entrypoints, tech stack, commands, tests, risks, and safe next steps.

• dev-security-review

  Use to review software security across auth, permissions, input validation, secrets, dependencies, workflows, and config.

• dev-spec-driven-implementation

  Use to implement a scoped multi-step change from an existing spec, handoff, issue, or explicit delivery request. Do not trigger for read-only analysis, planning, or a trivial localized edit.

• dev-test-strategy

  Use to design or validate test plans, unit/integration/e2e coverage, automation, CI checks, fixtures, and regression scope.

• office-briefing-note

  Use when producing concise decision-ready briefing notes from processed research materials.

• office-meeting-summary

  Use when converting meeting notes, transcripts, or chat logs into minutes, decisions, action items, and open questions.

• office-ppt-outline

  Use when turning materials into a presentation storyline, slide outline, speaker notes, or sharing-session structure.

• office-project-report

  Use when drafting project status reports, milestone reports, risk summaries, or management updates from provided materials.

• office-weekly-report

  Use when drafting or reviewing weekly reports from provided materials, progress logs, meeting notes, or team updates.

• research-evidence-table

  Use when building a claim/evidence/source table from provided research materials.

• research-source-dedup

  Use when deduplicating overlapping research materials, AI notes, excerpts, transcripts, and source packs.

• research-synthesis

  Use when turning mapped evidence and provided materials into a balanced research synthesis.

• sdlc-architecture-decision-record

  Use to record ADRs covering choices, tradeoffs, alternatives, consequences, status, and links to requirements/design evidence.

• sdlc-brd-workflow

  Use to draft or refine BRDs for business problem, goals, value, constraints, metrics, risks, and investment rationale.

• sdlc-change-control

  Use only when the user explicitly invokes this skill to manage an approved or proposed baseline/scope change across artifacts, traceability, approvals, and handoff.

• sdlc-dev-handoff-planning

  Use to create dev handoff packages and task cards from scoped SDLC materials, issues, specs, validation, and blockers.

• sdlc-domain-boundary-modeling

  Use to model bounded contexts, capabilities, ownership, domain data/language, allowed interactions, and forbidden dependencies.

• sdlc-hld-workflow

  Use to create or refine HLD from SRS, NFRs, domain boundaries, repo evidence, and architecture goals.

• sdlc-lld-workflow

  Use to create or refine LLD for modules, interfaces, state machines, data structures, errors, transactions, and tests.

• sdlc-manager

  Use only when the user explicitly invokes this skill to plan and route a multi-artifact SDLC/ADS workstream without automatically invoking downstream skills.

• sdlc-modular-monolith-architecture

  Use to design modular monolith boundaries, module layout, dependency rules, shared/platform seams, and extraction triggers.

• sdlc-nfr-spec

  Use to define measurable NFRs for performance, reliability, security, privacy, accessibility, observability, and operations.

• sdlc-prd-workflow

  Use to draft or refine PRDs covering product goals, scope, features, user flows, priorities, exceptions, and acceptance criteria.

• sdlc-project-research

  仅在用户明确要求基于仓库证据生成项目功能能力地图、能力盘点或持久研究包时使用；不要用于普通代码探索、repo onboarding、Git 历史问答或只读解释。

• sdlc-readiness-review

  Use only when the user explicitly invokes this skill to make a readiness-gate judgment on SDLC materials, specs, handoffs, issues, or direct-dev requests.

• sdlc-requirements-traceability

  Use to build or audit RTM links across requirements, design, validation, tasks, PRs, commits, releases, and evidence gaps.

• sdlc-requirements-workflow

  Use only when the user explicitly invokes this skill to establish a coordinated requirements baseline spanning business, user, and product inputs.

• sdlc-router

  Use only when the user explicitly invokes this skill to decide whether work needs SDLC/ADS and which minimum materials, if any, are justified.

• sdlc-solution-spec-workflow

  Use only when the user explicitly invokes this skill to coordinate a multi-artifact solution package across HLD, LLD, domain, ADR, NFR, and SPEC slices.

• sdlc-spec-slice-writer

  Use to write focused implementation SPEC slices for UI, API, data, admin, permissions, directory, observability, or release.

• sdlc-srs-workflow

  Use to draft or audit SRS with requirement IDs, functional requirements, acceptance criteria, constraints, NFR hooks, and traceability.

• sdlc-urs-workflow

  Use to draft or refine URS covering users, roles, jobs, scenarios, constraints, value, and acceptance-relevant outcomes.

• sdlc-validation-plan-workflow

  Use to create validation plans or behavior baselines linking requirements to checks, evidence, gaps, risks, and release gates.

Similar plugins