Graft

Repository-specific loop orchestrator for Graft multi-agent tasks. Use when one bounded task should run through repeated same-session serial worker-subagent rounds of `graft-multi-agent-task` under the default `topic-completion-loop` mode until the topic reaches `archive-ready`, becomes `blocked`, or no remaining batches stay in scope.

Repository-specific multi-agent coordination workflow for Graft. Use when the user explicitly wants subagent delegation, or when the current task cleanly splits into two or more disjoint slices across server, web, docs, or automation, and the main agent should keep ownership of review, validation, and final integration. `graft-boot` should assess whether this skill is justified before delegation starts.

Repository-specific workflow wrapper for Graft multi-agent tasks. Use when a task should be executed through `graft-multi-agent-batch`, and the slice may need `graft-task-closeout` plus `graft-commit` to finish with a safe handoff after validation.

Repository-specific end-of-task closeout workflow for Graft. Use when a task slice is ending and the agent needs to decide whether to emit only a next-step startup prompt or to commit the current validated slice first and then hand off safely. This is the default slice-end path for work started through `graft-boot`.

Manage reusable Graft AI-agent worktrees through guarded status, acquire, and release commands without treating directories or task branches as long-lived ownership.

Repository-specific Playwright browser workflow for inspecting, authenticating into, and interacting with the local Graft web UI. Use when Codex needs Graft browser screenshots, DOM text snapshots, login/auth verification with temp credentials, or simple click/fill/wait checks before normal web validation.

Inspect numbered Graft worktrees, compare task branches with the integration checkout, obtain explicit confirmation, and safely release and rebuild only stale or already-integrated slots. Use when cleaning abandoned agent worktrees, resolving unreleased feature slots, or deciding whether a numbered worktree can return to its main-XX pool marker.

Repository-specific push workflow for Graft. Use when the user explicitly wants the current branch pushed, or when a local push path is blocked and the agent needs to diagnose hook failures, upstream ambiguity, or remote rejection without inventing a second commit workflow.

Repository-specific scoped commit workflow for Graft. Use when the user explicitly wants the current validated task slice committed, or when `graft-task-closeout` decides a validated owned scope should be committed, and the agent needs to classify ownership, verify scope, choose a compliant Conventional Commit message, and create a safe git commit without bundling unrelated changes.

Repository-specific GitHub PR review workflow for the Graft repo. Use when Codex needs to inspect the GitHub pull request for the current branch, extract AI review findings from CodeRabbit, greptile-apps, gemini-code-assist, or github-advanced-security, read failed checks, MegaLinter warnings, or failed test signals from the PR, and then verify which findings should be fixed in the local codebase.

Repository-specific workflow for Graft cache governance. Use when a task adds or changes runtime read paths, system config consumption, RBAC/menu/bootstrap aggregation, dashboard summaries, container runtime views, notification gating, scheduler defaults, or other hotspot data that may require caching.

Repository-specific workflow for Graft localization and i18n changes. Use when adding or changing server i18n facade behavior, locale resource files, message keys, JSON Schema x-i18n metadata, web locale catalogs, locale aggregation, or key-first localization governance.

Govern high-value Chinese comments in Graft handwritten Go, TypeScript, and Vue code. Use when adding, updating, reviewing, or removing code comments, package documentation, Vue component documentation, TSDoc, or when closing any task that changes .go, .ts, or .vue files.

Classify Graft navigation, UI routes, object capabilities, and global pages before changing menus, route metadata, bootstrap navigation, or page entry points. Use for new or moved menu items, UI route migrations, global pages, and navigation design review.

Repository-specific workflow for creating or modifying Graft live Atlas/PostgreSQL migration SQL with Chinese database comments, globally unique versions, live/legacy boundaries, and deterministic validation.

Repository-specific audit workflow for Graft AI governance. Use when evaluating or changing AI tooling, MCP adoption, repository skills, ai-plan governance, Python helper scripts, environment inventory, or drift between AGENTS.md and AI workflow documents.

Repository-specific workflow for Graft ai-plan governance. Use when a docs/automation task changes ai-plan router documents, active-topic recovery materials, templates, catalog coverage, or bounded ai-plan validators without creating a second startup, validation, or recovery path.

Repository-specific startup workflow for Graft. Use when the task starts from a short prompt such as "boot", "continue", "read AGENTS", or "next step", and Codex should first ground itself in AGENTS.md, the ai-plan/ documents, the current repo state, assess whether multi-agent work is justified, and then enter implementation with the repository's closeout and commit workflow in place.

Repository-specific workflow orchestrator for new long-running work. Use when startup discovers a request that may need design, topic, roadmap, ADR, bootstrap, or loop dispatch, and the repository must classify it through one Work Intake path instead of special-case entry flows.

Repository-specific workflow for installing, registering, initializing, validating, or troubleshooting CodeGraph MCP for Graft. Use when the task mentions CodeGraph, codegraph init, codegraph serve --mcp, MCP navigation, /mcp missing codegraph, or turning CodeGraph setup into a repeatable repository workflow.

Use before adding, moving, renaming, removing, or replacing reusable Graft frontend/backend/cross-boundary assets so agents discover existing shared assets and maintain the curated shared asset registries without turning them into source inventories.

Repository-specific workflow for Graft database table design and migration governance. Use when designing or changing DB tables, Ent schemas, Atlas migrations, audit fields, soft delete fields, deleted_by, indexes, partial unique indexes, store query semantics, or database table and column comments.

Repository-specific frontend workflow for Graft web pages, shell surfaces, visible copy, and AI prompt shaping. Use when a task should first declare a page type, choose one of the first-stage built-in page masters or register an extension type, then implement token-driven, theme-responsive, i18n-safe UI in TDesign Vue Next.

Build or reshape Graft admin frontend pages using Vue 3, TypeScript, TDesign Vue Next, Pinia, Vue Router, Axios, UnoCSS, Graft page-type governance, and TDesign MCP. Use instead of generic Frontend App Builder, Frontend Design, Impeccable UI, Theme Factory, landing-page, or React/Tailwind/shadcn builder skills for Graft web work.

Repository-specific workflow for triaging, remediating, validating, and closing Graft GitHub Code Scanning and Dependabot alerts, including branch hygiene, scoped fixes, commit/push/PR flow, and post-push security recheck.

Scaffold or shape a new Graft server plugin before implementation. Use when adding a backend capability that should live under server/plugins, and Codex needs to define the plugin lifecycle, dependencies, public service boundaries, permissions, menus, migrations, routes, jobs, and validation scope in the repository's standard pattern.

Scaffold or shape a new Graft web module before implementation. Use when adding a Vue 3 admin feature under web/src/modules and Codex needs to align menu, route, page, api, and permission boundaries with the backend plugin contract and the repository's TDesign-based frontend conventions.

Normalize external frontend website-building, vibe-coding, UI generation, design-system, animation, screenshot, Playwright, Figma, accessibility, or asset-generation skill requests against Graft repository governance. Use before applying article-derived frontend skills, third-party frontend advice, or generic website-builder workflows to Graft web work.

Decide when Graft frontend work may use generated bitmap assets, existing visual assets, icons, or motion/animation guidance. Use for conditional Imagegen, UI Animation, asset, hero, illustration, empty-state, icon, transition, or motion requests in Graft web tasks while preserving admin-product restraint and repository asset governance.

Verify Graft frontend changes with repository-approved browser inspection, screenshots, DOM checks, accessibility-oriented review, and frontend validation. Use as the Graft replacement for generic Frontend Testing Debugging, Playwright, Screenshot, or AccessLint skills, without adding Playwright test dependencies or changing web/package.json.

Intake Figma links, screenshots, design exports, or design notes as reference material for Graft frontend work. Use when a user provides Figma-derived input, but keep repository docs, existing code, Graft page-type governance, and TDesign Vue Next authority above Figma. Do not add Figma SDKs or make Figma the source of truth.

Choose and run the smallest correct validation for Graft work. Use when the task touches server, web, automation, or cross-boundary contracts and Codex needs to decide which current validation commands are justified, which ones are not yet possible, and how to report validation gaps honestly.

Use when adding or modifying system config definitions, system config schemas, or system config edit/render UI in Graft.

Repository-specific pull-request creation workflow for Graft. Use when the user explicitly wants a PR created or reconciled for the current branch, or when the agent needs to safely create, reuse, or diagnose the current branch PR against the repository default branch without bypassing push, commit, or auto-merge safety gates.

Capture reusable engineering lessons at task closeout, route them into lessons/design/AGENTS with explicit thresholds, and prevent governance bloat.