🏷️ Go Function Rename Plan
Package Analyzed: pkg/linters/seenmapbool
Analysis Date: 2026-08-30
Round-Robin Position: package 116 of 187 total packages
Functions Analyzed: 8 functions across 1 files
Why This Matters
When AI coding agents search for functions to complete a task, they rely on function
names to understand what code does. Clear, descriptive names increase the likelihood
that an agent will find the right function instead of reimplementing existing logic.
Functions in the same package also call each other, so reviewing them together gives
better context for rename decisions.
Rename Suggestions
pkg/linters/seenmapbool/seenmapbool.go
| Current Name |
Suggested Name |
Reason |
run() |
analyzeSeenMapBoolUsage() |
The analyzer entrypoint currently uses a very generic verb. The new name makes it easier for an agent searching for the package's top-level analysis routine to find the function immediately. |
inspectBody() |
reportSeenMapBoolSetUsageInBody() |
The current name only says it inspects a body, not what it is looking for. The new name exposes both the reporting behavior and the map-as-set concern. |
findNonSetMaps() |
findCandidateMapsUsedBeyondSetSemantics() |
The current name is understandable but underspecified. The new name clarifies that the function filters candidate maps by detecting uses that go beyond pure set-style true assignments. |
markIfNonSetLiteral() |
markCandidateMapIfCompositeLiteralUsesNonTrueValue() |
The current name hides the composite-literal-specific behavior. The new name helps an agent find the helper when looking for logic that disqualifies candidate maps based on literal contents. |
All functions in this file (for reference):
init() — ✅ Clear, standard Go initialization hookrun() — ⚠️ Rename suggested (see table above)inspectBody() — ⚠️ Rename suggested (see table above)collectSeenMapCandidates() — ✅ Clear, no change neededfindNonSetMaps() — ⚠️ Rename suggested (see table above)markIfNonSetLiteral() — ⚠️ Rename suggested (see table above)isMapStringBool() — ✅ Clear, no change neededisBoolTrue() — ✅ Clear, no change needed
🤖 Agentic Implementation Plan
Agentic Implementation Plan
This issue is designed to be assigned to a coding agent. The agent should implement
all rename suggestions below in a single pull request.
Prerequisites
Implementation Steps
For each rename suggestion, follow this sequence:
1. Rename the function in pkg/linters/seenmapbool/seenmapbool.go
// Old
func oldName(args) returnType {
// New
func newName(args) returnType {2. Update all call sites
Use grep to find every caller and update the reference:
grep -rn "oldName" pkg/ --include="*.go"
Also check test files:
grep -rn "oldName" pkg/ --include="*_test.go"
3. Verify compilation after each rename
4. Run tests after all renames are complete
Suggested rename sequence and call sites
run → analyzeSeenMapBoolUsage
- Update analyzer registration in
pkg/linters/seenmapbool/seenmapbool.go
inspectBody → reportSeenMapBoolSetUsageInBody
- Update the call from the analyzer traversal in the same file
findNonSetMaps → findCandidateMapsUsedBeyondSetSemantics
- Update the local helper call in the same file
markIfNonSetLiteral → markCandidateMapIfCompositeLiteralUsesNonTrueValue
- Update both helper call sites in the same file
Commit Convention
Each rename should be a focused commit:
refactor: rename <oldName> to <newName> for clarity
Validation Checklist
Notes for the Agent
- This is a pure rename refactor — behavior must not change, only names
- If a rename causes unexpected complexity (e.g., name conflicts, interface constraints),
skip it and leave a comment in the PR explaining why
- Follow existing naming conventions documented in
AGENTS.md
- Unexported functions used only as closures or immediately-invoked can be skipped
Generated by the Daily Go Function Namer workflow
Run: 33309508896
Generated by 🔧 Daily Go Function Namer · pi · gpt54 · 13.3 AIC · ⌖ 9.54 AIC · ⊞ 8.9K · ◷
🏷️ Go Function Rename Plan
Package Analyzed:
pkg/linters/seenmapboolAnalysis Date: 2026-08-30
Round-Robin Position: package 116 of 187 total packages
Functions Analyzed: 8 functions across 1 files
Why This Matters
When AI coding agents search for functions to complete a task, they rely on function
names to understand what code does. Clear, descriptive names increase the likelihood
that an agent will find the right function instead of reimplementing existing logic.
Functions in the same package also call each other, so reviewing them together gives
better context for rename decisions.
Rename Suggestions
pkg/linters/seenmapbool/seenmapbool.gorun()analyzeSeenMapBoolUsage()inspectBody()reportSeenMapBoolSetUsageInBody()findNonSetMaps()findCandidateMapsUsedBeyondSetSemantics()trueassignments.markIfNonSetLiteral()markCandidateMapIfCompositeLiteralUsesNonTrueValue()All functions in this file (for reference):
init()— ✅ Clear, standard Go initialization hookrun()—inspectBody()—collectSeenMapCandidates()— ✅ Clear, no change neededfindNonSetMaps()—markIfNonSetLiteral()—isMapStringBool()— ✅ Clear, no change neededisBoolTrue()— ✅ Clear, no change needed🤖 Agentic Implementation Plan
Agentic Implementation Plan
This issue is designed to be assigned to a coding agent. The agent should implement
all rename suggestions below in a single pull request.
Prerequisites
Implementation Steps
For each rename suggestion, follow this sequence:
1. Rename the function in
pkg/linters/seenmapbool/seenmapbool.go2. Update all call sites
Use
grepto find every caller and update the reference:Also check test files:
3. Verify compilation after each rename
4. Run tests after all renames are complete
Suggested rename sequence and call sites
run→analyzeSeenMapBoolUsagepkg/linters/seenmapbool/seenmapbool.goinspectBody→reportSeenMapBoolSetUsageInBodyfindNonSetMaps→findCandidateMapsUsedBeyondSetSemanticsmarkIfNonSetLiteral→markCandidateMapIfCompositeLiteralUsesNonTrueValueCommit Convention
Each rename should be a focused commit:
Validation Checklist
make buildpasses with no errorsmake test-unitpassesmake lintpassesNotes for the Agent
skip it and leave a comment in the PR explaining why
AGENTS.mdGenerated by the Daily Go Function Namer workflow
Run: 33309508896