atlassian-suite

PR logic-bug scanner. Single responsibility — finds correctness errors only (off-by-one, null/undefined handling, race conditions, resource leaks, wrong operators, type confusion). Spawned by code-review-orchestrator with a target PR + file list. Read-only. Returns structured findings with confidence ≥ 80.

PR API contract & backward compatibility scanner. Single responsibility — finds breaking changes to public interfaces, request/response shape drift, schema breaks, deprecation gaps, and consumer impact. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR database scanner. Single responsibility — finds problematic queries, migrations, indexing issues, locking risks, and data-consistency problems. Spawned by code-review-orchestrator on diffs touching db/migration/query files. Read-only. Confidence ≥ 80.

PR financial-app scanner. Single responsibility — finds money/ledger/auth/audit/idempotency/reconciliation risks specific to financial systems. Spawned conditionally by code-review-orchestrator when the diff touches payment/billing/ledger/wallet code OR the project marks itself as financial. Read-only. Confidence ≥ 80.

PR observability scanner. Single responsibility — finds gaps in logs, metrics, traces, and error visibility that will make production debugging hard. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR conventions/patterns scanner. Single responsibility — finds violations of project rules, naming conventions, anti-patterns, duplication, dead code, magic numbers. Reads project rules from .claude/rules/ if present. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR performance & scalability scanner. Single responsibility — finds hot-path regressions, unnecessary allocations, complexity blowups, async/sync mistakes, resource leaks, scalability issues. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR rollout & operational safety scanner. Single responsibility — finds risky configuration defaults, missing feature flags on risky changes, dependency churn, and rollout/recovery gaps. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR security scanner. Single responsibility — finds security vulnerabilities only (injection, auth/authz bypass, hardcoded secrets, crypto misuse, unsafe deserialization, input validation gaps, path traversal, SSRF). Spawned by code-review-orchestrator. Read-only. Returns findings with confidence ≥ 80.

PR silent-failure scanner. Single responsibility — finds code that fails quietly (empty catches, swallowed errors, masked failures, retries that hide root cause). The most underreported bug class. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR spec compliance scanner. Single responsibility — maps acceptance criteria from the linked Jira issue(s) to the PR's code, flags missing implementations and over-building (functionality beyond spec). Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

PR test quality scanner. Single responsibility — finds missing critical-path coverage, weak assertions, missing edge cases, brittle tests, missing error-path tests. Cross-references test files with implementation. Spawned by code-review-orchestrator. Read-only. Confidence ≥ 80.

You are the Release Orchestrator for the Acendas Atlassian Suite. You compose, document, and publish releases by intersecting Bitbucket, Jira, and Confluence.

You are the Sprint Orchestrator for the Acendas Atlassian Suite. You own Jira Agile sprint workflows: planning, in-flight management, retros, and standup briefs.

You are the Triage Orchestrator for the Acendas Atlassian Suite. You handle bulk and structured Jira issue work: triage, creation, linking, watchers, batch transitions.

You are the Router for the Acendas Atlassian Suite. Your job is to dispatch work to the right specialist orchestrator, or — when no single specialist fits — to coordinate a multi-specialist workflow.

Use this agent for autonomous, multi-step code review work on Bitbucket pull requests with Jira context. Owns the multi-scanner pipeline (security, bugs, silent failures, patterns, tests, spec) plus deep-dive investigators and an adversarial critic. Trigger on phrases like "review PR

You are the DevOps Orchestrator for the Acendas Atlassian Suite. You own Bitbucket Pipelines, deployments, environments, branch protection, code insights, and related CI/CD plumbing.

You are the Knowledge Orchestrator for the Acendas Atlassian Suite. You own Confluence read, write, and edit operations: pages, spaces, comments, labels, attachments, version history.

Adversarial PR critic with anti-sycophancy directive. Challenges PRs against their Jira spec using assumption extraction, pre-mortem narrative, and structured criteria. Surfaces blind spots the scanners miss. Read-only. Spawned by code-review-orchestrator on high-stakes PRs (large diff, payments/auth/data, or release-bound).

Deep-dive investigator for a single high-stakes PR review finding. Receives ONE finding from a scanner and confirms or refutes it with evidence — reads call sites, traces data flow, checks tests, examines git blame on the destination branch. Returns a verdict (CONFIRMED / REFUTED / NEEDS-USER) with evidence. Spawned by code-review-orchestrator after Wave 1 scanners.

This skill should be used when the user asks to "audit branch protection", "show branch restrictions", "protect main branch", "require approvals", "branch policy", or runs `/atlassian-suite:branch-protection`. Lists branch restrictions on a repo and helps add/remove protection rules.

This skill should be used when the user asks to "search code", "find usages of X across repos", "where is function Y defined", "grep across bitbucket", or runs `/atlassian-suite:code-search`. Runs a Bitbucket workspace-wide code search with optional language/path/repo filters.

This skill should be used when the user asks to "show commit", "what changed in commit X", "commit details", "show me commit Y", or runs `/atlassian-suite:commit-show`. Pulls a commit's metadata, diff, diffstat, and CI/build statuses.

This skill should be used when the user asks to "list confluence attachments", "show attachments on page", "delete confluence attachment", or runs `/atlassian-suite:confluence-attachment`. Lists or deletes attachments on a Confluence page.

This skill should be used when the user asks to "comment on confluence page", "reply to confluence comment", "leave feedback on confluence", or runs `/atlassian-suite:confluence-comment`. Adds a footer comment or threaded reply to a Confluence page (Markdown body, converted to ADF).

This skill should be used when the user asks to "edit a section of a confluence page", "append to confluence page", "replace text on confluence", "update one paragraph on confluence", "fix typo on confluence page", "insert section after heading", "remove section from page", or runs `/atlassian-suite:confluence-edit`. Performs SURGICAL edits that preserve all other content (images, macros, charts). Always preferred over full-page rewrites unless replacing the entire page.

This skill should be used when the user asks to "show confluence page X", "read this confluence page", "rewrite confluence page", "create a child page", or runs `/atlassian-suite:confluence-page`. Reads a page or performs a FULL-PAGE rewrite/create. For partial edits (sections, find/replace, append), prefer `/atlassian-suite:confluence-edit`.

This skill should be used when the user asks to "search confluence", "find confluence page about X", "help me write CQL", "look up our docs on Y", or runs `/atlassian-suite:confluence-search`. Translates natural-language queries to CQL, runs the search, summarizes results.

This skill should be used when the user asks to "show confluence space structure", "list pages in space", "browse confluence tree", "what's under this confluence page", or runs `/atlassian-suite:confluence-tree`. Renders the page hierarchy of a Confluence space (or sub-tree under a page).

This skill should be used when the user asks to "create a jira issue", "file a bug in jira", "create a story", "open a ticket from this", or runs `/atlassian-suite:create-issue`. Creates a Jira issue with smart defaults pulled from current context (project, type, summary, description, labels), then asks once for confirmation.

This skill should be used when the user asks "what's deployed", "list deployments", "show environments", "deployment status", "promote to staging", or runs `/atlassian-suite:deployments`. Inspects Bitbucket Deployments — environments, recent deploys, and per-environment variables.

This skill should be used when the user asks to "init atlassian", "initialize atlassian", "setup atlassian", "configure atlassian", "configure jira/confluence/bitbucket", "set my atlassian credentials", "save atlassian credentials", "what credentials does the atlassian plugin need", "rotate my atlassian token", "remove atlassian credentials", or runs `/atlassian-suite:init`. Walks the user through configuring credentials for the Acendas Atlassian Suite — file-based by default, env-var fallback for CI.

This skill should be used when the user asks to "show jira issue X", "open PROJ-123", "what's the status of {issue}", "transition this issue", "comment on issue", or runs `/atlassian-suite:jira-issue`. Loads a Jira issue, displays a compact summary, and offers next actions (comment, transition, log work).

This skill should be used when the user asks to "link issues", "issue X blocks Y", "add issue link", "remove issue link", "list link types", or runs `/atlassian-suite:jira-link`. Creates and removes typed links between Jira issues.

This skill should be used when the user asks to "manage sprint", "create a sprint", "add issues to sprint", "start/close sprint", "list sprints", or runs `/atlassian-suite:jira-sprint`. Handles sprint lifecycle on a Scrum board (list/create/start/close, add/remove issues).

This skill should be used when the user asks to "log work on issue", "add worklog", "track time", "I spent 2h on PROJ-123", or runs `/atlassian-suite:jira-worklog`. Adds time entries to Jira issues and shows existing worklogs.

This skill should be used when the user asks to "search jira", "run a JQL query", "find jira issues where X", "help me write JQL", or runs `/atlassian-suite:jql-search`. Translates natural-language queries into JQL, runs the search, and explains the results.

This skill should be used when the user asks to "link this PR to a jira issue", "link pr to jira", "associate PR with ticket", "add Jira link to PR", or runs `/atlassian-suite:link-pr-to-issue`. Establishes a bidirectional link between a Bitbucket pull request and a Jira issue (issue gets a remote link to the PR; PR description and branch reference the issue key).

This skill should be used when the user asks for "pipeline status", "build status", "list pipelines", "is the build green", "show CI runs", or runs `/atlassian-suite:pipeline-status`. Lists recent Bitbucket Pipelines runs and summarizes pass/fail/in-progress.

This skill should be used when the user asks to "trigger a pipeline", "run a build", "start CI", "trigger custom pipeline", or runs `/atlassian-suite:pipeline-trigger`. Triggers a Bitbucket Pipelines build on a branch/commit/tag, optionally selecting a custom pipeline pattern with variables.

This skill should be used when the user asks to "create a PR", "open pull request", "raise PR", "create bitbucket PR from current branch", or runs `/atlassian-suite:pr-create`. Creates a Bitbucket PR with default reviewers, source/destination branches, and a Jira-aware description.

This skill should be used when the user asks to "create jira issues from review findings", "spin out follow-ups from PR review", "convert review notes to tickets", "file the follow-up bucket", "create issues for the follow-ups", or runs `/atlassian-suite:pr-followup`. Converts the follow-up bucket from a PR review into Jira issues with batch confirmation.

This skill should be used when the user asks to "list PRs", "list pull requests", "show open PRs", "PRs needing my review", "my PRs", or runs `/atlassian-suite:pr-list`. Lists Bitbucket pull requests with smart filters (mine, needs-review, stale).

This skill should be used when the user asks to "post pr summary to jira", "summarize this pr in jira", "comment pr status on jira issue", or runs `/atlassian-suite:pr-summary-to-jira`. Generates a concise PR status summary and posts it as a Jira comment on the linked issue, keeping non-technical stakeholders updated without leaving Jira.

This skill should be used when the user asks to "publish release notes to confluence", "post the changelog to confluence", "publish to confluence", "create confluence release notes page", "post release notes", or runs `/atlassian-suite:publish-release-notes`. Creates or updates a Confluence page with release notes in the chosen space.

This skill should be used when the user asks to "generate release notes", "draft release notes", "what changed in this release", "changelog from PRs and Jira", or runs `/atlassian-suite:release-notes`. Builds release notes by intersecting merged Bitbucket PRs in a date or commit range with their linked Jira issues, grouped by issue type.

This skill should be used when the user asks to "review this PR", "review pull request", "deep review of PR X", "review with full pipeline", "thorough code review", "release-readiness review", or runs `/atlassian-suite:review-pr`. Runs the multi-agent code review pipeline (6 specialized scanners + investigator + critic) against a Bitbucket PR with Jira context. Auto-selects scope and stakes.

This skill should be used when the user asks for "sprint retro", "retrospective brief", "sprint review summary", "what went well/poorly this sprint", or runs `/atlassian-suite:sprint-retro`. Produces a retro-ready brief from completed/incomplete work, scope churn, cycle-time outliers, and recurring blockers in a closed sprint.

This skill should be used when the user asks for "sprint status", "current sprint progress", "where are we in the sprint", "sprint health check", or runs `/atlassian-suite:sprint-status`. Produces a concise sprint progress report with completed/in-progress/blocked breakdown, scope changes, and burndown signal.

This skill should be used when the user asks for "standup notes", "what did I do yesterday", "daily standup", "yesterday/today/blockers", or runs `/atlassian-suite:standup-notes`. Generates a personalized daily standup brief from the user's Jira activity, in-flight Bitbucket PRs, and any blockers in the active sprint.

This skill should be used when the user asks to "triage this issue", "triage the bug", "categorize this jira ticket", "find related docs and prs for this issue", or runs `/atlassian-suite:triage-issue`. Pulls related Confluence docs and Bitbucket PRs/commits for a Jira issue, suggests labels/priority/component, and proposes a transition.