# Introduction Alright, so you’ve worked through the workbook. You now know how to: * assess your anxiety using the SUDS, * decrease your physiological arousal using TIPP, * challenge your biased thoughts using cognitive restructuring, and * actively engage with code reviews using DEAR and GIVE. Now what? Well, first of all, nice work! This workbook had a lot of information to get through and required you to take the time to face your code review anxiety, which isn’t easy! To really super-charge this work, though, you’ll need to **regularly practice all that you’ve learned during your code reviews**. Since it’s not the most convenient thing to work through the entire workbook over and over again, we’ve created a **Mini Code Review Anxiety Toolkit**. Think of this toolkit as a cheat sheet resource that reminds you to put everything you’ve learned into action at the exact moment in time that you need it. You can bookmark the [Toolkit here in GitBook](/code-review-anxiety-workbook-1/part-three-mini-code-review-anxiety-toolkit/mini-toolkit.md), or use the PDF version we created for your convenience: {% file src="/files/K0ePYm1ZFAN5S1lNrFM5" %} Save the PDF to your desktop, print it out and hang it somewhere near your monitor, or re-create it in a journal. Heck, you could even add some of the principles here - like the *acting like a DEAR* and *reviewing to GIVE* skills - to your code review templates in GitHub or GitLab so that the whole team keeps these top of mind. Regardless of how you choose to incorporate the Toolkit into your workflow, it’s yours to use for your next code review and beyond! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://developer-success-lab.gitbook.io/code-review-anxiety-workbook-1/part-three-mini-code-review-anxiety-toolkit/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.