菜单
Generate a custom /approve skill for your project. Ensures your source control, CI, and PR conventions are configured via /q-which-tools, then writes a tailored skill that verifies checks and merges approved PRs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Scan the current project and create a summary of its structure, important files, and conventions in .quiddity/project.md.
Generate a custom /next-task skill for your project. Ensures your issue tracker, source control, and CI are configured via /q-which-tools, then writes a tailored skill that picks up the next task, implements it, and opens a PR.
Generate a custom /new-issue skill for your project. Ensures your issue tracker is configured via /q-which-tools, then writes a tailored skill that converts plain-English descriptions into well-structured issues.
Run the full Quiddity setup flow. Discovers your process and tools, then generates custom /new-issue, /next-task, and /approve skills for your project.
Walk through the tools in .quiddity/tools.json and help install any missing CLIs or MCPs. Run /q-which-tools first if tools.json doesn't exist.
Discover what tools a project uses and save the configuration to .quiddity/tools.json. Pass category names as arguments (e.g., /q-which-tools issues source-control).
| name | q-setup-approve |
| description | Generate a custom /approve skill for your project. Ensures your source control, CI, and PR conventions are configured via /q-which-tools, then writes a tailored skill that verifies checks and merges approved PRs. |
You are generating a custom /approve skill for the user's project.
This skill needs the following tools.json categories: source-control, ci, pr
Ensure tools are configured. Check if .quiddity/tools.json exists and
contains the source-control, ci, and pr categories. For any missing
categories, run /q-which-tools with those categories (e.g.,
/q-which-tools source-control ci pr).
Read the configuration. Load all available Quiddity context:
.quiddity/project.md — project structure, CI/CD configuration.quiddity/process.md — merge strategy, review requirements,
post-merge workflow.quiddity/tools.json — extract the source-control, ci, and
pr categoriesAsk skill-specific questions not covered by tools.json:
/approve 123)
Or default to the current branch's PR?Generate the skill. Write a complete /approve SKILL.md to the
project's skills directory. The generated skill should:
.quiddity/tools.json for all tool-specific configurationShow the generated skill to the user and ask for confirmation before finalizing.
The generated /approve skill should follow this general structure, adapted
to the user's specific tools:
---
name: approve
description: Verify checks and merge an approved PR.
argument-hint: "[pr-number]"
---
# /approve
[Instructions tailored to the user's source control, CI checks,
merge strategy, and post-merge workflow.]