Copies the files you select into one AI-ready prompt, with a ===== path ===== header per file and an estimated token count. Binary files, files over 1 MB and build folders are left out, and the notification tells you which ones and why. Unsaved edits are included.
Finds API keys, tokens, private keys and passwords in your code and in your recent Git history, and tells you which commit, file and author added each one. Highlights secrets as you type and writes a masked CSV report you can share. Runs entirely on your machine.
Catches the .env mistakes that break a deploy or leak a key: keys missing from .env.example, real keys pasted into the example file, .env files that Git is not ignoring, and ones still in the Git history. Creates .env.example from .env with the values removed. Runs entirely on your machine.
Lets AI coding agents (Claude Code, Codex or any MCP client) see the IDE with screenshots, run safe IDE commands, prove that tests really ran from the JUnit reports, and share locks so parallel sessions don't run the same heavy task at once. Adds tools to the IDE's built-in MCP server; runs locally. Details for agents and developers.
Review pull requests from your self-hosted Gitea or Forgejo server inside the IDE: list them, open the changes in the IDE diff viewer, comment on a line, approve, request changes and merge. AI coding agents can read the unresolved review comments through the IDE's built-in MCP server. The access token is kept only in the IDE password safe. Details and setup.
Opens Excel .xlsx files as editable tables in the IDE (edit cells, insert and delete rows, switch sheets, undo, save), and lets AI coding agents read any cell range of a workbook as CSV through the IDE's built-in MCP server. .csv files are left alone. Runs entirely on your machine.
Catches test runs that look green but did not really test your code: 0 tests ran, every test was skipped, far fewer tests ran than last time, or the code changed after the run. Warns in the IDE and gives AI coding agents a test_run_verdict tool to call before they report that tests pass.
Finds every place where a project you copied from another project or template still carries the old name. One search covers every spelling (MyApp, my_app, my-app, my.app) in file contents and in file and folder names, and groups the results: shipped and public text, identifiers and config, tests and checks, build and scripts. AI coding agents can run the same search with the find_copy_leftovers tool through the IDE's built-in MCP server. It only reads the files of the open project.
Shows whether your tests really protect a line: it breaks the line on purpose (flips a comparison, && / ||, true / false, + / -, a number, or removes the statement), runs your test command and restores the file byte for byte. Works with any language and test runner. AI coding agents can call the mutation_spot_check tool through the IDE's built-in MCP server; it runs only the test command you saved in the IDE.
Finds your own computer's user name and home-folder paths (C:\Users\you\..., /home/you/..., /Users/you/...) in source files, configs and docs, and inside the ZIP or JAR you are about to publish. Such paths reveal your name and break on every other machine and on CI. An editor inspection marks them as you type, and you can add your own terms such as a company name or internal host names. AI coding agents can run the same search with the find_local_path_leaks tool through the IDE's built-in MCP server. It only reads the files of the open project and does not send them anywhere.
Finds garbled text (mojibake) and lost non-English characters in a project: text that a script, a shell command or a tool wrote back in the wrong encoding. It compares changed files with the last git commit to find characters that turned into ? and files that are no longer UTF-8, finds garbled sequences such as é by a round trip through the legacy encoding, and repairs the ones whose original can be recovered, after showing every replacement. AI coding agents can run the same search with the find_garbled_text tool through the IDE's built-in MCP server. It does not send your files anywhere.
Support is provided by email only: gramshift.official@gmail.com. Please include your IDE name and version, the plugin version, and what you expected to happen.
Licensing, trials, invoices and refunds are handled by JetBrains Marketplace.