- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add tobihagemann/turbo --skill create-project-skills -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add tobihagemann/turbo --skill create-project-skills -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add tobihagemann/turbo --skill create-project-skills -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add tobihagemann/turbo --skill create-project-skills -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/tobihagemann/turbo/tree/HEAD/claude/skills/create-project-skills게시자 제공
Generates one skill per detected convention area in the project's skill directory so future Claude or Codex sessions auto-load them when working in the repo.
At the start, use TaskCreate to create a task for each phase:
/write-skill skillIf $ARGUMENTS specifies paths, scope the scan to those paths; otherwise scan the whole repository.
Build the extraction context:
package.json, Cargo.toml, pyproject.toml, go.mod, Package.swift, pom.xml, Gemfile, and others appropriate to the stack).CLAUDE.md, .claude/rules/, AGENTS.md, and any .cursor/rules or .cursorrules. Note the conventions already documented there. The generated skills must not duplicate them..claude/skills/ (Claude Code), .agents/skills/ (Codex), and a top-level skills/ directory (match case-insensitively so Skills/ or similar non-standard casing is detected too). Resolve symlinks so co-linked paths are treated as one logical location.AskUserQuestion to confirm where generated skills should live. List each distinct resolved location as an option, noting any symlink alias in the option description. If .claude/skills/ is not among the detected locations, include it as a default option. The auto-added "Other" option lets users specify a custom path such as a project-specific directory.## section heading from the body. These signals feed rename-conflict detection in Step 3.Output a short text summary of detected stack, top-level layout, chosen target directory, and existing skills before moving on.
When that summary shows no source code to extract conventions from, stop here rather than dispatching Step 2. Executable code in any language qualifies, including scripts no manifest declares, so judge from the directory map rather than the detected stack. Documentation, instruction files, and configuration alone do not: extraction run over prose returns that prose's assertions as observed conventions, and Step 3 scores them with no code sites to test them against.
State that as text first — what the survey found, and that conventions extracted from it would have nothing to verify against. Then use AskUserQuestion to offer:
On the first option, run the /write-skill skill directly on that knowledge and skip the remaining steps. On either of the first two, mark the extraction phases cancelled so they no longer read as pending work.
Read references/pattern-extractor.md to see the full taxonomy of pattern categories. Decide which categories apply to the detected stack (e.g., drop "Styling and UI" for a backend service, drop "State management" for a static-analysis tool).
Emit all extraction Agent tool calls below in one assistant message. Each Agent call uses model: "opus" and no name. Wait for every agent to report before continuing. Do not begin the next step on a partial set, and do not relaunch an agent that has not yet reported. Launch one Agent per applicable category and state the total count explicitly when emitting the calls. Every agent's prompt must direct it to treat the shared working tree and its git index as read-only and to extract by reading and reasoning. Every agent's prompt must also direct it to search the repository with a tool that skips gitignored files, such as git grep --untracked or the Grep tool, and to open or search a gitignored path only when its prompt or a file its prompt directs it to read names it, or when a dependency's installed source is needed to verify a claim, never one holding local configuration or credentials. HEAD stays where it is: read other refs with git show <ref>:<path> rather than git checkout or git switch. Each agent's prompt must:
CLAUDE.md and .claude/rules/ so duplicates are skipped${CLAUDE_SKILL_DIR}/references/pattern-extractor.md as its role brief and return findings in the format defined at the end of that fileAggregate findings from all agents. For each finding, score three axes:
Group the surviving findings by topic into candidate skills. Each candidate typically covers one category, but related categories may merge if the patterns are tightly coupled. Split a candidate into two skills if its patterns cover clearly distinct sub-topics.
For each candidate skill, produce:
name (kebab-case, narrow to the topic, e.g., swift-naming, react-state, api-clients)file:line)If rename-conflict detection is ambiguous from the Step 1 signals alone, read the existing skill's SKILL.md body and compare convention statements before finalizing the Status tag.
Output the full proposal as text first, not inside AskUserQuestion. For each candidate skill, show:
After all candidates are listed, use AskUserQuestion to confirm the proposal with these options: "Approve all", "Make edits", "Cancel". If the user selects "Make edits", continue in conversation so the user can specify which candidates to drop, merge, or rename before returning here.
For each Rename conflict candidate, use a separate AskUserQuestion asking whether to update the existing skill, create the new one alongside it, or skip. Add a Get a second opinion option as a fourth choice, since creating alongside always establishes a second skill covering the same conventions. It runs the /consult-codex skill for which resolution leaves the skill set coherent. Then resolve the conflict with that answer in hand, re-asking when the choice stays the user's.
/write-skill SkillBuild the batch from approved candidates only. Do not include anything not explicitly approved in Step 4.
Output all approved candidates (both New and Update status) as text in a single batch. For each candidate, list the Status tag, proposed name, description, target path <target-skill-directory>/<name>/SKILL.md, and the 3–8 convention statements organized under ## <Section> headings with inline evidence citations (file_path:line). These convention statements define the target state the final SKILL.md should match, regardless of whether the skill is being created or updated.
Run the /write-skill skill once with this batch in context.
After /write-skill completes, output a summary of created and updated skills, grouped by status. If any candidates were dropped or skipped in Step 4, list them so the user knows what was left out.
CLAUDE.md or .claude/rules/. Reference them instead if needed.Scan a codebase and generate project skills capturing its inferred conventions. Use when the user asks to \"create project skills\", \"extract skills from the codebase\", or \"codify patterns as skill
---name: create-project-skillsdescription: Scan a codebase and generate project skills capturing its inferred conventions. Use when the user asks to…---# claude/skills/create-project-skills/SKILL.md개요
Scan a codebase and generate project skills capturing its inferred conventions. Use when the user asks to \"create project skills\", \"extract skills from the codebase\", or \"codify patterns as skills\".
FAQ
게시자에게서 claude/skills/create-project-skills/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/tobihagemann/turbo에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.