• There are 14 files with 515 lines of code.
• 0 very long files (0 lines of code)
• 0 long files (0 lines of code)
• 1 medium size files (372 lines of code)
• 0 small files (0 lines of code)
• 13 very small files (143 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
gatehouse.ts in cdk/lib	372	~2k–7k	6	~50	~7
V202601121111__create_user_permissions.sql in db/migrations	14	under 1k	1	~20	~1
V202511171406__create_user_sequence.sql in db/migrations	3	under 1k	2	~5	~1

Tokens are lines × 7 to 14 (analysis.fileReadsForChanges). Lines edited per change are the file's lines added and deleted divided by its commits over the whole history. Agents read about 2,000 lines at a time: when a 17,000-line file was split into modules, the tokens an agent read for the same change fell by 83% (The Economic Benefit of Refactoring, 2026).

There are 2 files with lines longer than 120 characters. In total, there are 2 long lines.

File	# lines	# units	# long lines
V202502251530__puzzle_id_column.sql in db/migrations	20	-	1
V202502031121__db_users_schema.sql in db/migrations	35	-	1

• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.