一键导入
project-setup
Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Navigate building a user-facing feature in the Reborn stack (a capability that crosses product_workflow → composition → webui_v2 → runtime/serve → frontend). Use when planning or implementing any new Reborn settings page, endpoint, facade method, or runtime-backed capability — especially before writing code, to avoid rebuilding what already exists and to wire it in one pass instead of layer-by-layer.
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Generate or update the IronClaw architecture overview video using Remotion. Use when asked to update, regenerate, or modify the architecture video, add/remove scenes, or reflect codebase changes in the video.
Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_reborn_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.
Use when starting work in the IronClaw repo, deciding where a feature/fix/prompt/doc belongs, tracing how a request flows, looking up which crate owns a subsystem, or when repo docs, the knowledge graph, or component names seem stale, missing, or contradictory.
| name | project-setup |
| version | 0.1.0 |
| description | Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope. |
| activation | {"keywords":["add repo","add repository","add project","new repo","new project","track repo","setup repo","project setup","setup workflow"],"patterns":["(?i)(add|track|setup|install|enable) (repo|repository|project)\\s","(?i)add .+/.+ to my workflow","(?i)set ?up (workflow|automation) for .+/.+"],"tags":["developer","github","setup"],"max_context_tokens":1500} |
| requires | {"skills":["github","github-workflow"]} |
Add a new GitHub repository as a tracked project in the workspace and install workflow automation.
Extract owner/repo from the user's message. If ambiguous, ask. Validate via GitHub API: http(method="GET", url="https://api.github.com/repos/{owner}/{repo}"). If 404 or no access, tell the user.
staging if yes)Read main_branch from the API response's default_branch field.
Write projects/<owner>-<repo>/project.md:
---
type: project
repo: <owner/repo>
added_at: <today YYYY-MM-DD>
maintainers: [<handles>]
main_branch: <branch from API>
staging_branch: <branch or null>
ai_agent_authors: [<bot handles>]
workflow_installed: false
---
# <owner/repo>
<description from API response>
## Workflow missions
(populated after install)
Write projects/<owner>-<repo>/notes.md:
# Notes: <owner/repo>
Developer notes for this project. Searchable via memory_search.
Follow the github-workflow skill's install procedure. For each of the 6 mission templates in github-workflow/references/workflow-routines.md:
{{repository}} with owner/repo{{slug}} with <owner>-<repo>{{maintainers}} with the maintainer list{{main_branch}} and {{staging_branch}} with the configured branches{{batch_interval_hours}} with 8 (default)mission_create(name, goal, cadence) for eachIf staging_branch is null, skip wf-staging-review-<slug>.
After installing, update the project file:
workflow_installed: true## Workflow missionsAdded <owner/repo> as a tracked project:
- Project file: projects/<owner>-<repo>/project.md
- Workflow missions installed: <list>
- Maintainers: <list>
- Main branch: <branch>, Staging: <branch or "none">
- This repo is now included in your morning brief and triage scans
Say "add repo <another/repo>" to add more, or "remove repo <owner/repo>" to uninstall.