Skip to content
| Marketplace
Sign in
Visual Studio Code>SCM Providers>JiraQuillNew to Visual Studio Code? Get it now.
JiraQuill

JiraQuill

Intellio AI

|
3 installs
| (0) | Free
JiraQuill by Intellio AI — pick a Jira issue, AI-generate the commit message, and drop KAN-123 <message> into the Source Control box.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

JiraQuill

by Intellio AI

Write great commit messages tied to your Jira issues — in one click. JiraQuill reads your staged changes, asks your editor's built-in AI to write a Conventional-Commits message, prefixes it with the Jira issue key, and can move the issue forward in your workflow after you commit.


Requirements

  • An editor with a built-in AI provider (enabled and signed in). JiraQuill uses whichever AI model your editor exposes.
  • A Jira Cloud account and an API token (created during setup).
  • A Git repository open in your editor.

Install

In VS Code, open Extensions (Ctrl+Shift+X), search JiraQuill, and click Install.


Setup

The first time you open it, JiraQuill walks you through a short 5-step wizard (you can re-run it anytime from the Command Palette → JiraQuill: Run Setup):

  1. Jira site URL — e.g. https://your-site.atlassian.net
  2. Atlassian email
  3. Jira API token — create one at id.atlassian.com. Your details are verified with Jira before anything is saved.
  4. Model — pick from the AI models your editor offers (e.g. gpt-4o).
  5. Target status — pick the status issues should move to after you commit (e.g. In Review), or choose "Don't move issues automatically".

How to use

  1. Stage your changes (the + in Source Control).
  2. Click the JiraQuill button in the Source Control panel title bar.
  3. Pick the Jira issue this commit is for.
  4. JiraQuill fills the commit box with KEY, <message> — review it, then press Commit.
  5. If you set a target status, the issue moves there automatically once the commit lands.

The message describes what actually changed in your staged code; the Jira issue is used for context and the key is added for you.


Your keys & privacy

Your credentials stay yours. JiraQuill is built so secrets never leak:

  • Your Jira API token is stored in your operating system's secure keychain (via VS Code Secret Storage) — never in settings, files, logs, or your commits. Clear it anytime with JiraQuill: Reset saved Jira token, or wipe all saved data with JiraQuill: Reset everything.
  • No AI API key is ever stored. Commit messages are generated through your editor's own AI sign-in.
  • What's sent, and where: only your staged diff and the selected issue's summary are sent to your editor's AI to write the message (capped at 12k characters). Your Jira URL, email, and token are used solely to talk to your Jira site over HTTPS only.
  • Nothing else leaves your machine. JiraQuill ships with zero third-party dependencies.

Commands

Open the Command Palette (Ctrl+Shift+P) and type "JiraQuill":

Command What it does
JiraQuill: Run Setup Re-run the setup wizard.
JiraQuill: Reset saved Jira token Remove the stored Jira token.
JiraQuill: Reset everything (show onboarding) Clear all saved settings and start fresh.

Settings

Setting Description
jiraCommit.baseUrl Your Jira site URL.
jiraCommit.email Your Atlassian account email.
jiraCommit.jql Which issues appear in the picker (defaults to your open, assigned issues).
jiraCommit.model AI model family (e.g. gpt-4o). Blank = any your editor provides.
jiraCommit.targetStatus Status issues move to after you commit. Blank = don't move.

License

MIT · © Intellio AI

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft