← All featuresAI Commit Assistant

Commit what you meant to commit. Nothing else.

Generate AI commit messages, catch leaked API keys before you commit, follow Conventional Commits or your own style, and fix failing Git hooks with AI.

The actual Changes panel with sample data. The secret scanner flags an API key in a changed line before it is committed. Select the image to enlarge.
WHY IT HELPS

The last look before a change becomes history.

Most commit mistakes are small and expensive: an API key pasted into a config file, an unsaved buffer left out of the change, a subject line that breaks the team's convention, or a pre-commit hook that fails with a wall of output. Flame's Changes panel puts those checks where you already review the diff. See the size of the change, catch likely secrets in the lines you changed, draft the message with AI in your team's style, and fix a failing hook without leaving the commit flow.

Catch leaked keys before the commit

The built-in scanner checks the lines you changed for likely credentials, such as cloud, GitHub, GitLab, npm, OpenAI, Anthropic, Stripe, and Slack tokens, private keys, and passwords in connection URLs. Click a finding to jump to the line.

Write the message in your team's style

Let AI read the diff and draft the commit message. Choose Conventional Commits, Task-first, Linux-kernel style, Semantic Commit Messages, or a custom convention with your own instructions and example.

Know what you are committing

The panel tracks files, added and removed lines, and size on disk as you work. Nested changes are grouped under their folders, and unsaved editor tabs are flagged with a one-click Save all.

Turn a failing hook into a fix

When a pre-commit or commit-msg hook blocks the commit, Flame shows why and offers Fix with AI. The hook output is staged in a chat for you to review; nothing is sent until you press Send.

AI COMMIT ASSISTANT IN PRACTICE

A secret scanner that reads the diff, not the whole repository.

Credentials usually leak one line at a time. Flame scans the changed lines in your working tree as you review them and shows a Potential secret in changed lines warning with the number of matches and files, before the commit or push carries them away.

Known token formats

Patterns cover AWS access keys, GitHub and GitLab tokens, npm and PyPI tokens, OpenAI, Anthropic, Hugging Face, and Google API keys, Slack, Stripe, SendGrid, Mailgun, Telegram, and Discord tokens, private key blocks, JWTs, and database or HTTP URLs with embedded passwords.

Suspicious assignments

Names such as api_key, client_secret, access_token, or password assigned a literal value are flagged too. References like process.env or import.meta.env are treated as placeholders, not secrets.

Review, then decide

Each finding names the file, line, and kind of secret. Jump to it, move the value into environment configuration, and rotate the credential if it was ever pushed. A warning is a prompt to look, not a guarantee that every secret was found.

AI COMMIT ASSISTANT IN PRACTICE

Conventional Commits, your task format, or a style of your own.

Teams agree on a commit style and then spend review time correcting it. In Flame, the convention is part of the commit form: it is checked as you type and it guides the AI when it drafts a message.

Built-in conventions

Choose Conventional Commits (type, optional scope, and description, such as feat(auth): add SSO login), Task-first with the exact task key and title, Linux-kernel style, or Semantic Commit Messages. Select the ? beside Convention to see each style explained with examples and documentation links.

Custom conventions

Open Settings → Git → Custom commit conventions to add a style with a name, an optional description, AI instructions, and an example. Turn on Use task ID and title and place <task-id> and <task-title> where your tracker reference belongs.

One style everywhere

Saved styles appear in both convention selectors and also guide Ask AI to commit, so a message drafted from the Changes panel and a commit prepared by an agent follow the same rules. Custom styles guide generation; they do not reject a summary you write by hand.

AI COMMIT ASSISTANT IN PRACTICE

Let AI read the diff and write the first draft.

A good commit message explains what changed and why. Generate commit message reads the selected changes and drafts a summary and description you can edit before committing.

Your model, saved per assistant

Right-click Generate commit message to choose a provider and model from the same catalog as AI Chat. The choice is saved under Settings → AI → Assistant models, so the commit assistant can use a fast model while chat uses another.

Fix the code you are looking at, then commit

After an AI edit, Flame offers the review: the changed file, its diff, and a commit message already written. Read it, adjust it, and commit when you agree.

Commit options in reach

Amend the last commit, sign off, use a prepared message, allow an empty commit, or skip Git hooks from the commit menu, without memorizing the flags.

AI COMMIT ASSISTANT IN PRACTICE

When a hook fails or a push needs options.

Pre-commit hooks protect the repository, but their failures can be hard to read. Pushing to a team's GitLab or GitHub remote often needs the same extra options every time.

Fix with AI for pre-commit and commit-msg hooks

A blocked commit shows the hook that stopped it and its output. Fix with AI prepares a chat with that output so the agent can correct a lint error, a formatting issue, or a message format. Review the change and commit again.

Custom push commands

Save push commands at global, group, or project scope, with environment variables, such as opening a GitLab merge request with push options or skipping CI for a documentation change. Run them from the push menu beside the standard Push and Force Push (Safe).

Keep the commit focused

Search changed files, check only the files that belong together, and read deleted files as read-only deletion diffs. Changed files group under their folders so a large change stays readable.

WATCH IT WORK

See the workflow in a short demo.

Official Flame demo · 1:09

Supercharge Your Commits: Secret Scanning, AI Messages & Hook Fixes

Diff size metrics, leaked API key detection before commit, unsaved buffer warnings, live commit convention checks, AI commit messages, one-click AI fixes for failing pre-commit hooks, and custom push commands.

HOW TO USE IT

From a working-tree change to a clean commit.

  1. Review the change set

    Open Changes to see the files, line deltas, and size on disk. Save any unsaved tabs the panel flags, and open each diff you want to inspect.

    The Changes panel and side-by-side diff with sample data.
  2. Resolve secret warnings

    If the scanner flags a potential secret, jump to the line, move the value out of source control, and confirm the warning clears.

  3. Write the message

    Pick the team's convention, then type the summary or select Generate commit message. Edit the draft until it says what the change does.

  4. Commit and push

    Commit with the options you need. If a hook fails, read the output or use Fix with AI. Push normally or run one of your saved custom push commands.

REQUIREMENTS & LIMITS

Know what the tool depends on.

  • Secret scanning uses known token formats and suspicious assignments in changed lines. It can miss secrets and flag safe values; it complements, not replaces, server-side secret scanning and credential rotation.
  • AI commit messages use the provider you select, so the diff is sent to that endpoint. Configure a local provider when your code must stay on the machine.
  • Custom conventions guide AI generation and Ask AI to commit. They do not validate summaries you type by hand.
  • Fix with AI prepares a chat with the hook output. It does not bypass the hook; review the agent's change and commit again.
FAQ

AI Commit Assistant: common questions