Integrations

Link Jira tickets to pull request reviews and verify that a PR actually meets the requirements on the ticket.

• Extracts Jira ticket IDs from PR titles and descriptions, PROJ-123, [PROJ-123], (PROJ-123), or several at once.
• Fetches ticket summary, description and acceptance criteria, and classifies the ticket type (Bug, Story, Task).
• Injects that context into the review so findings are judged against intended behavior.
• Setup: create an Atlassian API token, then add your Jira URL, email, token and project keys under Settings → Integrations and hit Test Connection.

Pull Linear issues and their PRDs into review, then write progress back to the issue.

• Detects Linear issue IDs (e.g. ENG-123) in PR titles and descriptions.
• Fetches the issue title, description, status and PRD, the linked project's content and attached Linear documents.
• Posts a requirements checklist on the PR showing which acceptance criteria are implemented.
• Writes back to Linear: a comment with the PR link, completed criteria struck through, and a move to In Progress.
• Setup: create a personal API key in Settings → Security & access; use a service account for org-wide use.

Search your Confluence space over MCP and pull the relevant requirement pages into the review prompt.

• Connects through an MCP server and calls tools such as confluence_search and confluence_read.
• An orchestration agent runs up to 3 rounds of tool calls to gather enough context from the PR title and description.
• Requirements are extracted verbatim, with the source page title and URL attached.
• API tokens are encrypted with Fernet symmetric encryption, never returned in plain text, and all traffic uses HTTPS.

Turn any finding into a tracked issue from the comment itself, no copy-pasting, no context switching.

• Create Issue opens an issue in the native platform: GitHub Issues, GitLab Issues, Bitbucket Issues, or an Azure DevOps work item.
• Create Jira Ticket opens a Jira Task in your configured project, formatted in Atlassian Document Format with file path, vulnerability type, description and code suggestion.
• Codity posts the Jira ticket URL back as a reply in the PR thread, so the link is visible to every reviewer.
• Native issues need no extra configuration; the Jira button appears once Jira integration is set up.

Codity review, security scanning, PR triage and fix workflows inside Claude Code, backed by the Codity CLI.

• /codity:review reviews local changes and helps fix findings.
• /codity:fix applies Codity PR comments with approval before each fix.
• /codity:check-pr waits for CI, reads review comments, and summarizes merge status.
• /codity:loop runs review → fix → re-review until critical and high findings are cleared, up to 5 iterations.
• Install with /plugin marketplace add codity-ai/codity-plugin then /plugin install codity@codity, and authenticate once with codity login in your own terminal.

The same four Codity skills inside Cursor Agent, installed from a repository marketplace or written by the CLI.

• Agent picks a skill from your request, or you invoke one with /code-review, /autofix, /check-pr or /codity-loop.
• Install by importing https://github.com/codity-ai/codity-plugin under Customize > From GitHub Repository, on any plan.
• Or run codity skill install --editor cursor to write the skills into .cursor/skills/ without a marketplace.
• Skills call the CLI with CODITY_NO_TTY=1 and read findings from codity review --full --json, so the agent never opens a terminal UI.
• Requires Cursor 2.4 for the CLI install, a newer build for the plugin flows, and one codity login in your own terminal.