autofix-bot-api
Use when scanning a repository or code change for security vulnerabilities, leaked secrets, or dependency issues via the Autofix Bot API (api.autofix.bot) and auto-applying detected fixes; requires AUTOFIX_BOT_API_KEY ; do NOT use for general code review without an Autofix Bot account ; returns findings report and applied-fix summary.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- autofix-bot-api
- description
- Use when scanning a repository or code change for security vulnerabilities, leaked secrets, or dependency issues via the Autofix Bot API (api.autofix.bot) and auto-applying detected fixes; requires AUTOFIX_BOT_API_KEY ; do NOT use for general code review without an Autofix Bot account ; returns findings report and applied-fix summary.
02 资源文件 2
- 参考文档_meta.json272 B
- 参考文档.clawhub/origin.json152 B
03 SKILL.md 正文
Autofix Bot API
Scan code for security vulnerabilities, secrets, and dependency issues via the Autofix Bot REST API, and auto-fix detected issues.
Authentication
All API calls require a Bearer token. Read the key from the AUTOFIX_BOT_API_KEY environment variable:
curl https://api.autofix.bot/workspace \
-H "Authorization: Bearer $AUTOFIX_BOT_API_KEY"
If the key is not set, ask the user to provide it. Never hardcode API keys or pass them as command-line arguments. All bundled scripts read from this environment variable automatically.
Workflow
Step 1: Create a repository
curl -X POST https://api.autofix.bot/repositories \
-H "Authorization: Bearer $AUTOFIX_BOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "my-repo",
"external_id": "local:my-repo",
"detection": ["security", "secrets"],
"fix": ["security", "secrets"]
}'
Save the returned id (e.g., repo_...). Use external_id to avoid duplicates — if a repo with the same external_id exists, retrieve it with GET /repositories/external:local:my-repo instead.
Step 2: Sync code
Use the bundled scripts/sync_repo.sh script:
# Full sync (first time)
./scripts/sync_repo.sh /path/to/repo <repo_id>
# Incremental sync (subsequent updates)
./scripts/sync_repo.sh /path/to/repo <repo_id> <base_ref>
The script creates a git bundle, obtains a signed upload URL, uploads the bundle, and polls until sync completes. It outputs the sync ID on success.
Step 3: Run analysis
Step 4: Poll for results
Step 5: Inspect results and apply fixes
Detection Categories
Key Patterns
API Reference
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files