--- title: "BugIt by Taskivator (@bugitdev) | Hashnode" description: "QA agent inside the AI assistant you already use. Made by Taskivator. Read the latest articles by BugIt by Taskivator on Hashnode." url: "https://hashnode.com/@bugitdev" --- @bugitdev # BugIt by Taskivator @bugitdev · Tokyo, Japan · Joined October 2026 QA agent inside the AI assistant you already use. Made by Taskivator. ### [Is it a bug, or is it the spec? Settle it before you file](https://bugit.hashnode.dev/is-it-a-bug-or-is-it-the-spec-settle-it-before-you-file?utm_source=hashnode&utm_medium=feed) Some of the longest ticket threads in any tracker are not about code at all. They are about whether the behaviour is wrong in the first place: "This is working as designed." "The design is wrong, the 3 min read · [bugit.hashnode.dev](https://bugit.hashnode.dev/is-it-a-bug-or-is-it-the-spec-settle-it-before-you-file?utm_source=hashnode&utm_medium=feed) [Oct 16](https://hashnode.com/posts/is-it-a-bug-or-is-it-the-spec-settle-it-before-you-file/6ad225a43cd54e27e5802bd3) ### [Severity is not priority: a practical guide for people who file bugs](https://bugit.hashnode.dev/severity-is-not-priority-a-practical-guide-for-people-who-file-bugs?utm_source=hashnode&utm_medium=feed) Most trackers have two fields that look like they mean the same thing: severity and priority. Teams that treat them as one end up arguing in triage about words instead of bugs. Teams that keep them ap 4 min read · [bugit.hashnode.dev](https://bugit.hashnode.dev/severity-is-not-priority-a-practical-guide-for-people-who-file-bugs?utm_source=hashnode&utm_medium=feed) [Oct 10](https://hashnode.com/posts/severity-is-not-priority-a-practical-guide-for-people-who-file-bugs/6aca09fa8befd0341e1e9a4e) ### [What to paste from a crash log (and what to leave out)](https://bugit.hashnode.dev/what-to-paste-from-a-crash-log-and-what-to-leave-out?utm_source=hashnode&utm_medium=feed) "Logs attached." Two words that appear in a great many bug reports, followed by a file of several thousand lines that nobody opens. The log was supposed to be the strongest evidence in the ticket. Ins 4 min read · [bugit.hashnode.dev](https://bugit.hashnode.dev/what-to-paste-from-a-crash-log-and-what-to-leave-out?utm_source=hashnode&utm_medium=feed) [Oct 9](https://hashnode.com/posts/what-to-paste-from-a-crash-log-and-what-to-leave-out/6ac83d6d2303272acaf25e73) ### [Before you file it: how to find the duplicate a newest first list hides](https://bugit.hashnode.dev/before-you-file-it-how-to-find-the-duplicate-a-newest-first-list-hides?utm_source=hashnode&utm_medium=feed) Most trackers have the same ghost: the bug that was reported eight months ago, triaged, discussed, half fixed, and then forgotten. Today someone hits it again and files a fresh ticket. Now the context 4 min read · [bugit.hashnode.dev](https://bugit.hashnode.dev/before-you-file-it-how-to-find-the-duplicate-a-newest-first-list-hides?utm_source=hashnode&utm_medium=feed) [Oct 6](https://hashnode.com/posts/before-you-file-it-how-to-find-the-duplicate-a-newest-first-list-hides/6ac4cd12c3f27420f0fffc29) ### [How to write a bug report developers can act on (with a free template)](https://bugit.hashnode.dev/how-to-write-a-bug-report-developers-can-act-on-with-a-free-template?utm_source=hashnode&utm_medium=feed) Most bug reports are not wrong. They are just not enough. "Checkout is broken" is true, and it starts a conversation instead of a fix: which checkout, which build, broken how, for whom? Each question 7 min read · [bugit.hashnode.dev](https://bugit.hashnode.dev/how-to-write-a-bug-report-developers-can-act-on-with-a-free-template?utm_source=hashnode&utm_medium=feed) [Oct 4](https://hashnode.com/posts/how-to-write-a-bug-report-developers-can-act-on-with-a-free-template/6ac237d6547904724e0dce1b)