Skip to content

carbon-language/carbon-lang / .agents/skills/agent_tools

Agent tools

Verified

Guidelines and restrictions on shell commands and file manipulation tools for AI assistants.

Agent tools

AI assistants working on the Carbon repository MUST NOT use legacy or generic UNIX shell search/edit commands when specialized environment tools exist.

Command line tools restrictions

  • DO NOT USE: cat, less, grep, sed, or other shell utilities for viewing, searching, or modifying files.
  • DO NOT USE: patch to write and apply patch files.
  • DO NOT USE: Writing custom scripts in other languages to circumvent this limitation.
  • DO USE: High-fidelity semantic API tools:
    • Viewing: Use view_file instead of cat / less.
    • Searching: Use grep_search / find_by_name instead of grep / find.
    • Modifying: Use replace_file_content, multi_replace_file_content, or write_to_file instead of sed / patch / python edits.

You may only write and run temporary programs to modify source code if no semantic tool is applicable or when performing complex, systematic transforms across many codebase directories simultaneously.

Temporary files management

Temporary files and scratchpad test scripts created by the assistant during analysis, experiments, or debugging:

  • MUST reside within the tmp/ subdirectory under the workspace root.
  • MUST be periodically cleaned out and deleted before ending your turn to preserve a clean git workspace.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall