القائمة
Configure a target project for the aiops bundle — issue tracker, triage labels, domain doc layout. Silent defaults on inline bootstrap; full prompts on explicit /aiops-setup.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | aiops-setup |
| description | Configure a target project for the aiops bundle — issue tracker, triage labels, domain doc layout. Silent defaults on inline bootstrap; full prompts on explicit /aiops-setup. |
| disable-model-invocation | true |
Scaffold per-repo config: issue tracker, triage labels, domain docs.
/aiops conductor)When docs/agents/ is missing:
aiops.yaml if present — see aiops-yaml.md.issue_tracker.kind: local, triage labels 1:1, domain.layout: single. Write docs/agents/* without asking.github or gitlab → seed matching issue-tracker-*.md; apply yaml prs_as_triage and label overrides. No A/B/C questionnaire unless yaml is incomplete.CLAUDE.md or AGENTS.md ## Agent skills block (create section if missing; ask only if neither file exists)./aiops-setup)Interactive — explore, confirm one section at a time, then write. Use when switching tracker or restarting config.
Check: aiops.yaml, git remote, AGENTS.md / CLAUDE.md, CONTEXT.md, CONTEXT-MAP.md, docs/adr/, docs/agents/, .scratch/.
Skip sections already satisfied by aiops.yaml — show yaml values and offer edit only.
A — Issue tracker: Only offer GitHub/GitLab in the questionnaire if user has no aiops.yaml and explicitly asks for remote tracker. Otherwise default local markdown.
B — Triage labels: Map five roles to tracker strings. Default 1:1.
C — Domain docs: Single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md).
D — Constitution: If CONSTITUTION.md does not exist at repo root, offer to generate one from constitution-template.md. Walk through each section (Testing, Code quality, Architecture, Performance, Security, Process) and ask the user to fill in project-specific principles. These are non-negotiable — referenced by every agent at every phase.
Show ## Agent skills block + docs/agents/issue-tracker.md, triage-labels.md, domain.md for user edit.
Seed templates: issue-tracker-*.md, triage-labels.md, domain.md. If constitution was configured, write CONSTITUTION.md from template with user's answers.
Point user to docs/agents/*.md. Optional: add aiops.yaml from aiops.yaml.example for reproducible team defaults.
Delivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval.
Flow Conductor for the aiops bundle. One entry — infers task type, shows plain-language steps, tracks journey in flow.state.yaml, dispatches skill + agent per phase.
Structured design process for the architect agent. Guides from grill conclusions to complete NOTES.md + tech-spec.md plus needed domain documentation updates through constraint gathering, module identification, interface design, alternative exploration, and risk analysis. Use when the architect needs to produce design decisions and technical specifications.
Build and query a persistent code graph for the target project. Uses graphify (Tree-sitter + Louvain clustering) for deterministic structural extraction, then the model adds semantic annotations. Use when the user says build graph, code graph, dependency graph, impact analysis, or when other skills need structured code understanding before proceeding.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user says architecture review, codebase health, deepening, refactor suggestions, or complains about architectural friction.
Review in three modes — code (diff vs standards/spec), design (NOTES + tech-spec before planning), drift (implementation vs tech-spec before ship). Pick mode from Flow Conductor phase or user intent; do not mix artifact types.