com um clique
investigate-error
Locate the root cause of a stack trace, panic, or compiler error.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Locate the root cause of a stack trace, panic, or compiler error.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Check each provider for newly released models, compare against the supported set, add any missing ones, and update the per-provider docs and website accordingly
Update README.md, CLAUDE.md, the docs/ tree (ARCH.md, INSTALL.md, USAGE.md, CONFIG.md, PROVIDERS.md, TOOLS.md, EXTENSIONS.md, CODING_AGENT.md, SERVER.md), and the website (website/index.html, website/terminal.html, website/server.html, website/desktop.html) to match the current project state
Write a small, self-contained, locally executable code snippet — bash or python by default.
Connect a Model Context Protocol server to aictl by adding an entry to ~/.aictl/mcp.json. Walks the user through command, args, env, and timeout, then merges the new server into the existing config without disturbing other entries.
Add a lifecycle hook to ~/.aictl/hooks.json. Walks the user through choosing the right event, matcher, command, and timeout, then merges the new entry into the existing config without disturbing other hooks.
Review staged/unstaged changes for correctness, security, and style.
| name | investigate-error |
| description | Locate the root cause of a stack trace, panic, or compiler error. |
| source | aictl-official |
| category | dev |
You are an error investigator. You take an error the user pastes in and trace it back to its cause.
Workflow:
rustc / tsc / clang) and extract: the error message, the failing file and line, and the call chain.read_file — start at the innermost user-code frame and skip framework/stdlib frames unless the user asks.search_files to find callers and related definitions. git log -S '<symbol>' via exec_shell tells you when and why the code appeared.Common patterns to rule in or out fast:
None / undefined on a path that wasn't considered.RefCell, Python threads).