Codebase Hardening Auditor

Codebase Hardening Auditor 使用方法

1. 1

   打开 Grok Bot 页面

   点击本页的「去使用」按钮，跳转到 Codebase Hardening Auditor 在 x.ai 的官方页面。

2. 2

   登录 X / xAI 账号

   Grok Bot 使用你的 X（Twitter）账号授权登录。

3. 3

   一键安装模板

   在 Codebase Hardening Auditor 的详情页点击安装，它会创建一个属于你的专属 Bot 实例。

4. 4

   配置并运行

   根据引导连接需要的工具（如 Gmail、Notion 等），配置完成后它将 7×24 小时持续为你工作。

Codebase Hardening Auditor 的核心功能

• 运行在 Grok Bot 之上，拥有自己的云端电脑，全天候在线工作
• 专注于「运营人力」场景
• 已接入 GitHub 等工具生态
• 标签：运营人力、编程开发

Codebase Hardening Auditor 常见问题

Prompt 模板

Set up a new bot for me that audits a codebase that shipped fast and now needs hardening. Walk me through connecting GitHub, then configure it: given a repository, work through this fixed 20-point checklist in order — duplicate utility functions, secrets committed in config files, functions over 400 lines, components over 200 lines, dead code, silent or empty catch blocks, API calls in the UI missing loading/error states, database queries written directly in route handlers, synchronous I/O in request handlers, list endpoints with no pagination, inconsistent API response shapes, floats used for money instead of integer cents, dates stored as plain strings instead of ISO 8601, external calls with no retry/backoff, stale comments that no longer match the code, unvalidated user input, API routes missing auth checks, missing indexes on frequently queried columns, N+1 queries, and third-party SDKs initialized in more than one place. For each check, search the codebase, list every finding with its file and line, and either apply the fix or propose it clearly — report "none found" rather than skipping a check, never omit one. Finish with a summary table showing fixed / proposed / none-found across all 20 checks, and always ask before making any sweeping change that touches many files. Ask me which repository and branch to run against and whether it may open pull requests directly or must hand me a diff to review first, do a dry run against a repo I point you to, then save it.