Update to Aikido Security

{
  "description": "Fetches comments already posted on a GitHub/GitLab/Azure DevOps pull or merge request (e.g. CI bot results, review feedback, Aikido's own scan-result comment). Use when the user asks what CI/CD said, wants to read/check/summarize PR or MR comments, mentions \"pipeline comments\", or asks about \"Aikido comments\"/\"Aikido feedback\"/what Aikido said or found on a PR — this reads via the native SCM CLI (gh/glab/az), not the Aikido MCP server.",
  "included_files": [
    {
      "relative_path": "reference.md",
      "size_in_bytes": 1711
    }
  ],
  "name": "pr-comments",
  "skill_md_contents": "---\nname: pr-comments\ndescription: Fetches comments already posted on a GitHub/GitLab/Azure DevOps pull or merge request (e.g. CI bot results, review feedback, Aikido's own scan-result comment). Use when the user asks what CI/CD said, wants to read/check/summarize PR or MR comments, mentions \"pipeline comments\", or asks about \"Aikido comments\"/\"Aikido feedback\"/what Aikido said or found on a PR — this reads via the native SCM CLI (gh/glab/az), not the Aikido MCP server.\n---\n\nReading CI/CD or Aikido comments on a pull/merge request means fetching whatever is already\nposted there through the repo's own SCM CLI. Don't route this through the Aikido MCP server,\nthe native CLI already does it in one call.\n\n## 1. Determine the target\n\n- If the user names a specific repo/PR (a URL, or `org/repo#123`), use that.\n- Otherwise, run `git remote get-url origin` in the current working directory and use the\n  current branch's PR/MR (the CLIs below auto-detect this when no number is given).\n\n## 2. Determine the platform\n\nMatch the remote host:\n- Contains `github` → **GitHub**, use `gh`.\n- Contains `gitlab` → **GitLab**, use `glab`.\n- Contains `dev.azure.com` or `visualstudio.com` → **Azure DevOps**, use `az`.\n\nIf the host matches none of these (e.g. self-hosted with a custom domain, or Bitbucket), stop\nand ask the user which platform it is, or tell them this skill only covers GitHub/GitLab/Azure\nDevOps.\n\n## 3. Fetch the comments\n\nRun the command directly, don't pre-check install or auth state first. See\n[reference.md](reference.md) for the exact command and flags per platform.\n\n## 4. Recover from failure\n\n- **Command not found**: don't install it yourself. Tell the user the CLI is missing, show the\n  install command from reference.md, and ask for permission before running it. Only proceed\n  once they say yes, then retry the same fetch.\n- **Auth error** (401/403, or the CLI reports not logged in): print the exact login command\n  for that platform, ask the user to run it (it's an interactive browser flow you can't\n  complete yourself), wait for their confirmation, then retry.\n\n## 5. Present the results\n\nList the comments in chronological order: author, timestamp, body. Don't filter out bot\ncomments or try to classify which ones are \"CI/CD\" versus human, just show the thread as-is.\n\n**Never:** call an Aikido MCP tool to satisfy this request, or fabricate comment content if\nthe fetch keeps failing, report the actual error instead.\n"
}