~ / rigs / reema14a / incidentops-skeleton

reema14a/incidentops-skeleton

A spec-driven, multi-agent framework for automated incident detection, triage, and resolution — built entirely inside Kiro IDE using its vibe coding, hooks, and MCP orchestration features.

↗ GitHub ★ 0 no license updated 12mo ago project Kiro
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~3.4k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 3/100 Guardrails v2

Copy this rig

$ git clone --depth 1 https://github.com/reema14a/incidentops-skeleton

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:

{
  "permissions": {
    "deny": [
      "Read(./.env)",
      "Read(./.env.*)",
      "Read(**/.env)",
      "Read(~/.ssh/**)",
      "Bash(git push --force:*)",
      "Read(**/*.pem)",
      "Read(.env)",
      "Read(~/.aws/**)",
      "Read(**/*.key)",
      "Read(**/.env.*)",
      "Bash(git push --force*)",
      "Bash(rm -rf:*)",
      "Bash(rm -rf *)",
      "Bash(sudo *)",
      "Bash(sudo:*)",
      "Bash(rm -rf /)",
      "Bash(git push -f:*)",
      "Read(.env.*)",
      "Bash(git reset --hard*)",
      "Bash(rm -rf /*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(gh pr merge *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(gh pr merge:*)",
      "Bash(gh pr create *)",
      "Bash(git reset --hard:*)",
      "Bash(npm publish:*)",
      "Bash(git rebase *)"
    ]
  }
}

Hooks (2)

eventmatcherruns
PostFileSaveagents/llm_governance_insights_agent.py,llm/local_mcp/tools/tarot_tool.py,orchestrator/orchestrator.pyA schema-defining file has been modified. Please perform the following tasks: 1. Analyze the changes to identify any modifications to output schemas, data structures, or required keys in: - Governance insights output (from llm_governanc
PostFileSaveorchestrator/orchestrator.pyReview the orchestrator.py file and verify that any Tarot Oracle MCP integration is fully optional and fault-tolerant. Check for: 1. **Error Handling**: All Tarot MCP calls must be wrapped in try-except blocks that catch and log errors wit

Kiro (4 steering · 1 specs · 2 hook files)

Specs: tarot-oracle (loaded on demand, not counted in context tax)

How Kiro files are scored: methodology.

Similar rigs

copied ✓