# Welcome to Hikeshi ## Introduction We're happy to see you're interested in trying out Hikeshi and hope you enjoy your stay. If you've got any questions, feel free to look at our FAQ or if you find an issue, open a Github Issue. ### Why the name "Hikeshi"? The name comes from the firefighting system established in Japan during the Edo period. Incident response involves a lot of "firefighting" in the sense that you're only called upon when something has gone very wrong. In high stress situations, it's nice to have a simple tool that assists you while you fight those fires. ### The Goal The primary hope for this application is to create a tool that doesn't get in the way or add to the stress of incident response. It aims to be simple, reliable, and unobtrusive. ### **TLDR** * No-cluttered UI. * No noisy in-app notifications. * Web Hooks allow you to notify in slack. * Dark mode support by default. * Designed specifically for incident response. It isn't feature packed, but it does exactly what it needs to while you take care of the incidents at hand. ## Github & GoDoc {% embed url="" %} View the source on Github {% endembed %} {% embed url="" %} View package docs on pkg.go.dev {% endembed %} --- # 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://brittonhayes.gitbook.io/hikeshi/undefined.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.