RepoPilot

fuellabs / sway

Search fuellabs/sway

GitHub

Code

How fuellabs/sway is laid out, and where to start for common changes.

There is no import map for this report yet.

Where to start reading

  1. Repository root
  2. Repository root
  3. Likely public API
  4. Likely public API
  5. Likely start-up file
  6. Likely start-up file

Find files for a task

AI

Add a New Forc CLI Command

  • Create new command handler file in forc/src/cli/commands/

Add a New Compiler Pass or Analysis

  • Implement pass logic following existing analysis pattern (e.g., call_graph.rs)

Add a New Forc Plugin

  • Create Cargo.toml and src/main.rs with forc-plugin integration
  • Register plugin in workspace Cargo.toml members list

Extend Sway Standard Library

  • Add new .sw module file in sway-lib-std/src/
  • Update sway-lib-std/README.md with documentation

Change the public API

Trace runtime behavior

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

  • Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

  • Branch points35 per file on average
  • Code issues0 errors, 46 warnings
  • Largest file3,676 lines
  • Hotspot load0 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions6 workflows
  • Tests6,477 test filesRust test · 9.3 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected

Test folders: forc-plugins/forc-doc/tests/fixtures/function_impls · forc-plugins/forc-doc/tests/fixtures/impl_traits_generic/src · forc-plugins/forc-doc/tests/fixtures/impl_traits/src

Hotspots

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.