devops

name	devops
description	OpsIntelligence DevOps skill graph — the entry point for PR review, SonarQube triage, CI/CD monitoring, incident response, and runbook execution. Lazy-load a specific node via read_skill_node("devops", "<node>").
user-invocable	false
metadata	{"opsintelligence":{"requires":{"tools":["devops.*"]},"primaryEnvs":["OPSINTEL_GITHUB_TOKEN","OPSINTEL_GITLAB_TOKEN","OPSINTEL_JENKINS_TOKEN","OPSINTEL_SONAR_TOKEN"]}}

DevOps — Map of Content

This is the entry node for the built-in DevOps graph. Evidence tools are read-only (PR metadata, diff, CI, Sonar, Jenkins). devops.github.pr_comment posts a PR conversation comment using the configured GitHub PAT when the user asks to publish feedback on the PR. Heavier writes (merge, approve, dismiss reviews, deploy) still require explicit human confirmation in the same turn.

How to use this graph

1. Read the team policy files loaded from teams/<active>/*.md. The team's PR / Sonar / CI rules are authoritative — this graph is generic.
2. Pick the node that matches the user's ask and call read_skill_node("devops", "<node>"):
   • [[pr-review]] — review a pull/merge request end-to-end.
   • [[sonar]] — interpret SonarQube results and gate decisions.
   • [[cicd]] — monitor GitHub Actions, GitLab CI, and Jenkins pipelines.
   • [[incidents]] — triage a production incident from page to postmortem.
   • [[runbooks]] — execute or author a runbook safely.
3. Use the devops.* tools registered in the tool catalog to fetch evidence (PRs, pipelines, jobs, quality gates) and, when appropriate, post a PR comment via devops.github.pr_comment. Quote sources; never invent IDs, SHAs, or run numbers.
4. Prefer delegating multi-step reasoning to a named smart prompt chain via the chain_run tool. Chains are bounded, self-critiquing pipelines and cost far fewer tokens than improvising the whole flow inline:
   • chain_run with id: "pr-review" and inputs including pr_url plus GitHub evidence strings from devops.github.pull_request / devops.github.pr_diff (see pr-review.md) → Ship/Hold verdict.
   • chain_run {id: "sonar-triage", inputs: {project_key: "..."}} → gate recommendation.
   • chain_run {id: "cicd-regression", inputs: {platform: "github", target: "owner/repo/ci.yml"}} → regression triage.
   • chain_run {id: "incident-scribe", inputs: {evidence: "..."}} → brief + update + postmortem skeleton.
   • chain_run {id: "meta/self-critique", kind: "prompt", inputs: {draft: "..."}} → pre-send critique. Call chain_list at runtime if the ids above are stale.

Output contract (applies to every node)

• Lead with a one-line verdict (e.g. Ship / Hold / Roll forward).
• Group findings under Blockers, Must-fix, Nits, or Action / Monitor / Skip — whatever the node specifies.
• Always link back to the source URL (PR, pipeline run, Sonar issue).
• Never paste raw tokens, secrets, cookies, or .env contents.

Safety posture

• Do not trigger a deploy, cancel a production pipeline, merge a PR, or silence a Sonar rule without an in-turn "yes" from a human.
• Summarize logs, do not quote them verbatim — they may contain PII.
• Respect owner-only paths under the state dir (POLICIES.md, RULES.md, policies/). You may read them; you may not write to them.

Companion skills

Built-in standalone skills the agent can invoke directly (alongside this graph):

• devops.github.pr_comment — post Markdown on the PR conversation thread using the gateway’s GitHub token (no gh binary). Use when the user asked to comment on the PR from chat/WhatsApp.
• gh-pr-review — full PR review workflow. If gh is installed and authenticated on the host (command -v gh && gh auth status), use the gh-based path for local checkout, worktrees, lint/test runs, and richer CLI output. If gh is not available (chat, WhatsApp, headless), use the API-only path inside the same skill: devops.github.pull_request → devops.github.pr_diff → devops.github.submit_review (posts body + inline comments + suggestions atomically via PAT, no binary needed). See the skill's path-selection table.
• devops.github.submit_review — the direct write tool for line-level reviews when gh is absent. Also usable alongside gh when you want a single atomic API call instead of shelling out.
• github — generic gh CLI cheat-sheet for everything that isn't PR-review-specific.
• gh-issues — auto-triage and auto-fix flows for GitHub Issues (advanced).

---

Related: [[pr-review]], [[sonar]], [[cicd]], [[incidents]], [[runbooks]].