What is Sensei?
The Sensei plugin provides an easy way to find specific code patterns in your source code, and then apply rewrite rules to amend the matching code. All within the Intellij IDE, and in real-time.
For example, you could create a rule that matches on JUnit `@Disabled` annotations which do not have a reason, Sensei would then tell you about the issue by highlighting the code in the IDE.
Additionally, when you `alt+enter`, you can have the option to `Add a todo comment parameter`.
When selected, this would amend the code to add a boilerplate reason, which you can then amend, and if you don't, it will show up in your TODO panel.
e.g. `@Disabled` would become ` @Disabled("TODO: add a description here")`
Sensei combines the functionality of a Static Analysis code scanner with a code rewriting engine.
IntelliJ Intention Actions
Based on the above description, the obvious alternative (if you were not using Sensei) is to use the IntelliJ Intention Actions functionality.
Sensei differs from IntelliJ Intention Actions because the aim with Sensei is to provide a way to create matchers and rewriters which are project specific, or even local to an individual developer.
We have tried to put together a GUI that makes both the matching and rewrite rules easy to write and experiment with.
How can it help me personally improve?
When I'm learning a new library, it takes me time to build up muscle memory around the methods and formatting. So I might choose to create personal recipes which
- link off to the official documentation or tutorial pages
- have boilerplate templates which are most effective
- fix poor coding practices
- add boilerplate code to help use a library
I can use Sensei to build temporary recipes which prompt me for the current practices I've chosen to use and help me build up effective habits. And the recipes are temporary because I can remove them when I outgrow them.
How can it help my team improve?
In the same way we can help teams build up muscle memory around agreed coding standards.
Creating cookbooks of recipes that we apply when we find the same comments in pull request reviews. Since the cookbooks are stored in version control with the project, they are available to everyone on the project. And we can switch them off when we no longer need prompting.
Sensei helps provide feedback early
What we've tried to build with Sensei is a way of pulling the feedback that helps us improve, and reminders of corrective action, as early into the coding process as we can.
Rather than wait for
- the results of a static analyser
- the comments from a code review
We can instead see the feedback, for custom standards we want to enforce, as we code.
And we have either reminders, or actual rewrite rules, to help us write code that complies with the standards.
Sensei is flexible
In that way, Sensei is a bit of a mix, since it's:
- part Static Analyser
- coding tutor
- rewrite engine
Sensei is flexible enough to make the job of saying "What is Sensei?" that little bit harder.
Sensei fills a gap in the programming workflow
We've tried to make Sensei the missing piece of the programmer workflow that helps you improve specific elements in your coding style, or library use, that you and your team are currently working with.
This flexibility means that it takes a little more time to get to grips with Sensei than a static analysis tool or the built-in IntelliJ Intentions. Still, by spending the time to experiment, you will gain a new way to speed up your learning in your personal development process.
How to experiment?
Once you have downloaded and installed Sensei from the [Intellij Marketplace]
The easiest way to make Sensei work for you is to look at your coding process and consider:
- What documentation do you keep looking up?
-- You could add some Sensei recipes that link back to that documentation. - What simple mistakes do you keep making?
-- You could temporarily codify that poor coding pattern as a matcher, and write a Quick Fix rewrite that amends the code to be what you really want to write. - What boilerplate code do you write to use a library?
-- You could create a Quick Fix rule to write the code for you.
Since Sensei is designed to work alongside whatever static analysis tool you're using, if you find that the same violations are being reported from static analysis, then you could replicate the condition in a Sensei recipe. You can then add a Quick Fix to help train you, not just to identify the mistake, but also to move quickly to writing the correct code
The Sensei plugin provides an easy way to find specific code patterns in your source code, and then apply rewrite rules to amend the matching code. All within the Intellij IDE, and in real-time.
Alan Richardson has more than twenty years of professional IT experience, working as a developer and at every level of the testing hierarchy from Tester through to Head of Testing. Head of Developer Relations at Secure Code Warrior, he works directly with teams, to improve the development of quality secure code. Alan is the author of four books including “Dear Evil Tester”, and “Java For Testers”. Alan has also created online training courses to help people learn Technical Web Testing and Selenium WebDriver with Java. Alan posts his writing and training videos on SeleniumSimplified.com, EvilTester.com, JavaForTesters.com, and CompendiumDev.co.uk.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demo
Alan Richardson has more than twenty years of professional IT experience, working as a developer and at every level of the testing hierarchy from Tester through to Head of Testing. Head of Developer Relations at Secure Code Warrior, he works directly with teams, to improve the development of quality secure code. Alan is the author of four books including “Dear Evil Tester”, and “Java For Testers”. Alan has also created online training courses to help people learn Technical Web Testing and Selenium WebDriver with Java. Alan posts his writing and training videos on SeleniumSimplified.com, EvilTester.com, JavaForTesters.com, and CompendiumDev.co.uk.
The Sensei plugin provides an easy way to find specific code patterns in your source code, and then apply rewrite rules to amend the matching code. All within the Intellij IDE, and in real-time.
For example, you could create a rule that matches on JUnit `@Disabled` annotations which do not have a reason, Sensei would then tell you about the issue by highlighting the code in the IDE.
Additionally, when you `alt+enter`, you can have the option to `Add a todo comment parameter`.
When selected, this would amend the code to add a boilerplate reason, which you can then amend, and if you don't, it will show up in your TODO panel.
e.g. `@Disabled` would become ` @Disabled("TODO: add a description here")`
Sensei combines the functionality of a Static Analysis code scanner with a code rewriting engine.
IntelliJ Intention Actions
Based on the above description, the obvious alternative (if you were not using Sensei) is to use the IntelliJ Intention Actions functionality.
Sensei differs from IntelliJ Intention Actions because the aim with Sensei is to provide a way to create matchers and rewriters which are project specific, or even local to an individual developer.
We have tried to put together a GUI that makes both the matching and rewrite rules easy to write and experiment with.
How can it help me personally improve?
When I'm learning a new library, it takes me time to build up muscle memory around the methods and formatting. So I might choose to create personal recipes which
- link off to the official documentation or tutorial pages
- have boilerplate templates which are most effective
- fix poor coding practices
- add boilerplate code to help use a library
I can use Sensei to build temporary recipes which prompt me for the current practices I've chosen to use and help me build up effective habits. And the recipes are temporary because I can remove them when I outgrow them.
How can it help my team improve?
In the same way we can help teams build up muscle memory around agreed coding standards.
Creating cookbooks of recipes that we apply when we find the same comments in pull request reviews. Since the cookbooks are stored in version control with the project, they are available to everyone on the project. And we can switch them off when we no longer need prompting.
Sensei helps provide feedback early
What we've tried to build with Sensei is a way of pulling the feedback that helps us improve, and reminders of corrective action, as early into the coding process as we can.
Rather than wait for
- the results of a static analyser
- the comments from a code review
We can instead see the feedback, for custom standards we want to enforce, as we code.
And we have either reminders, or actual rewrite rules, to help us write code that complies with the standards.
Sensei is flexible
In that way, Sensei is a bit of a mix, since it's:
- part Static Analyser
- coding tutor
- rewrite engine
Sensei is flexible enough to make the job of saying "What is Sensei?" that little bit harder.
Sensei fills a gap in the programming workflow
We've tried to make Sensei the missing piece of the programmer workflow that helps you improve specific elements in your coding style, or library use, that you and your team are currently working with.
This flexibility means that it takes a little more time to get to grips with Sensei than a static analysis tool or the built-in IntelliJ Intentions. Still, by spending the time to experiment, you will gain a new way to speed up your learning in your personal development process.
How to experiment?
Once you have downloaded and installed Sensei from the [Intellij Marketplace]
The easiest way to make Sensei work for you is to look at your coding process and consider:
- What documentation do you keep looking up?
-- You could add some Sensei recipes that link back to that documentation. - What simple mistakes do you keep making?
-- You could temporarily codify that poor coding pattern as a matcher, and write a Quick Fix rewrite that amends the code to be what you really want to write. - What boilerplate code do you write to use a library?
-- You could create a Quick Fix rule to write the code for you.
Since Sensei is designed to work alongside whatever static analysis tool you're using, if you find that the same violations are being reported from static analysis, then you could replicate the condition in a Sensei recipe. You can then add a Quick Fix to help train you, not just to identify the mistake, but also to move quickly to writing the correct code
The Sensei plugin provides an easy way to find specific code patterns in your source code, and then apply rewrite rules to amend the matching code. All within the Intellij IDE, and in real-time.
For example, you could create a rule that matches on JUnit `@Disabled` annotations which do not have a reason, Sensei would then tell you about the issue by highlighting the code in the IDE.
Additionally, when you `alt+enter`, you can have the option to `Add a todo comment parameter`.
When selected, this would amend the code to add a boilerplate reason, which you can then amend, and if you don't, it will show up in your TODO panel.
e.g. `@Disabled` would become ` @Disabled("TODO: add a description here")`
Sensei combines the functionality of a Static Analysis code scanner with a code rewriting engine.
IntelliJ Intention Actions
Based on the above description, the obvious alternative (if you were not using Sensei) is to use the IntelliJ Intention Actions functionality.
Sensei differs from IntelliJ Intention Actions because the aim with Sensei is to provide a way to create matchers and rewriters which are project specific, or even local to an individual developer.
We have tried to put together a GUI that makes both the matching and rewrite rules easy to write and experiment with.
How can it help me personally improve?
When I'm learning a new library, it takes me time to build up muscle memory around the methods and formatting. So I might choose to create personal recipes which
- link off to the official documentation or tutorial pages
- have boilerplate templates which are most effective
- fix poor coding practices
- add boilerplate code to help use a library
I can use Sensei to build temporary recipes which prompt me for the current practices I've chosen to use and help me build up effective habits. And the recipes are temporary because I can remove them when I outgrow them.
How can it help my team improve?
In the same way we can help teams build up muscle memory around agreed coding standards.
Creating cookbooks of recipes that we apply when we find the same comments in pull request reviews. Since the cookbooks are stored in version control with the project, they are available to everyone on the project. And we can switch them off when we no longer need prompting.
Sensei helps provide feedback early
What we've tried to build with Sensei is a way of pulling the feedback that helps us improve, and reminders of corrective action, as early into the coding process as we can.
Rather than wait for
- the results of a static analyser
- the comments from a code review
We can instead see the feedback, for custom standards we want to enforce, as we code.
And we have either reminders, or actual rewrite rules, to help us write code that complies with the standards.
Sensei is flexible
In that way, Sensei is a bit of a mix, since it's:
- part Static Analyser
- coding tutor
- rewrite engine
Sensei is flexible enough to make the job of saying "What is Sensei?" that little bit harder.
Sensei fills a gap in the programming workflow
We've tried to make Sensei the missing piece of the programmer workflow that helps you improve specific elements in your coding style, or library use, that you and your team are currently working with.
This flexibility means that it takes a little more time to get to grips with Sensei than a static analysis tool or the built-in IntelliJ Intentions. Still, by spending the time to experiment, you will gain a new way to speed up your learning in your personal development process.
How to experiment?
Once you have downloaded and installed Sensei from the [Intellij Marketplace]
The easiest way to make Sensei work for you is to look at your coding process and consider:
- What documentation do you keep looking up?
-- You could add some Sensei recipes that link back to that documentation. - What simple mistakes do you keep making?
-- You could temporarily codify that poor coding pattern as a matcher, and write a Quick Fix rewrite that amends the code to be what you really want to write. - What boilerplate code do you write to use a library?
-- You could create a Quick Fix rule to write the code for you.
Since Sensei is designed to work alongside whatever static analysis tool you're using, if you find that the same violations are being reported from static analysis, then you could replicate the condition in a Sensei recipe. You can then add a Quick Fix to help train you, not just to identify the mistake, but also to move quickly to writing the correct code
Click on the link below and download the PDF of this resource.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
View reportBook a demo
Alan Richardson has more than twenty years of professional IT experience, working as a developer and at every level of the testing hierarchy from Tester through to Head of Testing. Head of Developer Relations at Secure Code Warrior, he works directly with teams, to improve the development of quality secure code. Alan is the author of four books including “Dear Evil Tester”, and “Java For Testers”. Alan has also created online training courses to help people learn Technical Web Testing and Selenium WebDriver with Java. Alan posts his writing and training videos on SeleniumSimplified.com, EvilTester.com, JavaForTesters.com, and CompendiumDev.co.uk.
The Sensei plugin provides an easy way to find specific code patterns in your source code, and then apply rewrite rules to amend the matching code. All within the Intellij IDE, and in real-time.
For example, you could create a rule that matches on JUnit `@Disabled` annotations which do not have a reason, Sensei would then tell you about the issue by highlighting the code in the IDE.
Additionally, when you `alt+enter`, you can have the option to `Add a todo comment parameter`.
When selected, this would amend the code to add a boilerplate reason, which you can then amend, and if you don't, it will show up in your TODO panel.
e.g. `@Disabled` would become ` @Disabled("TODO: add a description here")`
Sensei combines the functionality of a Static Analysis code scanner with a code rewriting engine.
IntelliJ Intention Actions
Based on the above description, the obvious alternative (if you were not using Sensei) is to use the IntelliJ Intention Actions functionality.
Sensei differs from IntelliJ Intention Actions because the aim with Sensei is to provide a way to create matchers and rewriters which are project specific, or even local to an individual developer.
We have tried to put together a GUI that makes both the matching and rewrite rules easy to write and experiment with.
How can it help me personally improve?
When I'm learning a new library, it takes me time to build up muscle memory around the methods and formatting. So I might choose to create personal recipes which
- link off to the official documentation or tutorial pages
- have boilerplate templates which are most effective
- fix poor coding practices
- add boilerplate code to help use a library
I can use Sensei to build temporary recipes which prompt me for the current practices I've chosen to use and help me build up effective habits. And the recipes are temporary because I can remove them when I outgrow them.
How can it help my team improve?
In the same way we can help teams build up muscle memory around agreed coding standards.
Creating cookbooks of recipes that we apply when we find the same comments in pull request reviews. Since the cookbooks are stored in version control with the project, they are available to everyone on the project. And we can switch them off when we no longer need prompting.
Sensei helps provide feedback early
What we've tried to build with Sensei is a way of pulling the feedback that helps us improve, and reminders of corrective action, as early into the coding process as we can.
Rather than wait for
- the results of a static analyser
- the comments from a code review
We can instead see the feedback, for custom standards we want to enforce, as we code.
And we have either reminders, or actual rewrite rules, to help us write code that complies with the standards.
Sensei is flexible
In that way, Sensei is a bit of a mix, since it's:
- part Static Analyser
- coding tutor
- rewrite engine
Sensei is flexible enough to make the job of saying "What is Sensei?" that little bit harder.
Sensei fills a gap in the programming workflow
We've tried to make Sensei the missing piece of the programmer workflow that helps you improve specific elements in your coding style, or library use, that you and your team are currently working with.
This flexibility means that it takes a little more time to get to grips with Sensei than a static analysis tool or the built-in IntelliJ Intentions. Still, by spending the time to experiment, you will gain a new way to speed up your learning in your personal development process.
How to experiment?
Once you have downloaded and installed Sensei from the [Intellij Marketplace]
The easiest way to make Sensei work for you is to look at your coding process and consider:
- What documentation do you keep looking up?
-- You could add some Sensei recipes that link back to that documentation. - What simple mistakes do you keep making?
-- You could temporarily codify that poor coding pattern as a matcher, and write a Quick Fix rewrite that amends the code to be what you really want to write. - What boilerplate code do you write to use a library?
-- You could create a Quick Fix rule to write the code for you.
Since Sensei is designed to work alongside whatever static analysis tool you're using, if you find that the same violations are being reported from static analysis, then you could replicate the condition in a Sensei recipe. You can then add a Quick Fix to help train you, not just to identify the mistake, but also to move quickly to writing the correct code
Table of contents
Alan Richardson has more than twenty years of professional IT experience, working as a developer and at every level of the testing hierarchy from Tester through to Head of Testing. Head of Developer Relations at Secure Code Warrior, he works directly with teams, to improve the development of quality secure code. Alan is the author of four books including “Dear Evil Tester”, and “Java For Testers”. Alan has also created online training courses to help people learn Technical Web Testing and Selenium WebDriver with Java. Alan posts his writing and training videos on SeleniumSimplified.com, EvilTester.com, JavaForTesters.com, and CompendiumDev.co.uk.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demoDownloadResources to get you started
Secure by Design: Defining Best Practices, Enabling Developers and Benchmarking Preventative Security Outcomes
In this research paper, Secure Code Warrior co-founders, Pieter Danhieux and Dr. Matias Madou, Ph.D., along with expert contributors, Chris Inglis, Former US National Cyber Director (now Strategic Advisor to Paladin Capital Group), and Devin Lynch, Senior Director, Paladin Global Institute, will reveal key findings from over twenty in-depth interviews with enterprise security leaders including CISOs, a VP of Application Security, and software security professionals.
Benchmarking Security Skills: Streamlining Secure-by-Design in the Enterprise
Finding meaningful data on the success of Secure-by-Design initiatives is notoriously difficult. CISOs are often challenged when attempting to prove the return on investment (ROI) and business value of security program activities at both the people and company levels. Not to mention, it’s particularly difficult for enterprises to gain insights into how their organizations are benchmarked against current industry standards. The President’s National Cybersecurity Strategy challenged stakeholders to “embrace security and resilience by design.” The key to making Secure-by-Design initiatives work is not only giving developers the skills to ensure secure code, but also assuring the regulators that those skills are in place. In this presentation, we share a myriad of qualitative and quantitative data, derived from multiple primary sources, including internal data points collected from over 250,000 developers, data-driven customer insights, and public studies. Leveraging this aggregation of data points, we aim to communicate a vision of the current state of Secure-by-Design initiatives across multiple verticals. The report details why this space is currently underutilized, the significant impact a successful upskilling program can have on cybersecurity risk mitigation, and the potential to eliminate categories of vulnerabilities from a codebase.
Resources to get you started
Setting the Standard: SCW Releases Free AI Coding Security Rules on GitHub
AI-assisted development is no longer on the horizon — it’s here, and it’s rapidly reshaping how software is written. Tools like GitHub Copilot, Cline, Roo, Cursor, Aider, and Windsurf are transforming developers into co-pilots of their own, enabling faster iteration and accelerating everything from prototyping to major refactoring projects.
Close the Loop on Vulnerabilities with Secure Code Warrior + HackerOne
Secure Code Warrior is excited to announce our new integration with HackerOne, a leader in offensive security solutions. Together, we're building a powerful, integrated ecosystem. HackerOne pinpoints where vulnerabilities are actually happening in real-world environments, exposing the "what" and "where" of security issues.
Revealed: How the Cyber Industry Defines Secure by Design
In our latest white paper, our Co-Founders, Pieter Danhieux and Dr. Matias Madou, Ph.D., sat down with over twenty enterprise security leaders, including CISOs, AppSec leaders and security professionals, to figure out the key pieces of this puzzle and uncover the reality behind the Secure by Design movement. It’s a shared ambition across the security teams, but no shared playbook.
Is Vibe Coding Going to Turn Your Codebase Into a Frat Party?
Vibe coding is like a college frat party, and AI is the centerpiece of all the festivities, the keg. It’s a lot of fun to let loose, get creative, and see where your imagination can take you, but after a few keg stands, drinking (or, using AI) in moderation is undoubtedly the safer long-term solution.
Developer-driven coding.
Securely.
Contact us today and make software security an intrinsic part of your development process.
