Files

JiaJun f388aabfda feat(game): 更新游戏数据结构并优化历史记录显示

- 将动物图片资源配置重构为统一的花朵资源管理模块
- 添加奖励图片资源支持，实现动物和奖励图片的双重映射
- 在游戏历史记录中显示实际数字对应的奖励图标
- 修复历史记录中数字显示的空值处理逻辑
- 更新GitNexus项目索引统计信息
- 优化桌面游戏中花朵选择组件的渲染性能

2026-05-29 16:47:41 +08:00

2.6 KiB

Raw Blame History

GitNexus — Code Intelligence

This project is indexed by GitNexus as 36-character-flower (2527 symbols, 4819 relationships, 217 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.

If any GitNexus tool warns the index is stale, run npx gitnexus analyze in terminal first.

Always Do

MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run gitnexus_impact({target: "symbolName", direction: "upstream"}) and report the blast radius (direct callers, affected processes, risk level) to the user.
MUST run gitnexus_detect_changes() before committing to verify your changes only affect expected symbols and execution flows.
MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
When exploring unfamiliar code, use gitnexus_query({query: "concept"}) to find execution flows instead of grepping. It returns process-grouped results ranked by relevance.
When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use gitnexus_context({name: "symbolName"}).

Never Do

NEVER edit a function, class, or method without first running gitnexus_impact on it.
NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
NEVER rename symbols with find-and-replace — use gitnexus_rename which understands the call graph.
NEVER commit changes without running gitnexus_detect_changes() to check affected scope.

Resources

Resource	Use for
`gitnexus://repo/36-character-flower/context`	Codebase overview, check index freshness
`gitnexus://repo/36-character-flower/clusters`	All functional areas
`gitnexus://repo/36-character-flower/processes`	All execution flows
`gitnexus://repo/36-character-flower/process/{name}`	Step-by-step execution trace

CLI

Task	Read this skill file
Understand architecture / "How does X work?"	`.claude/skills/gitnexus/gitnexus-exploring/SKILL.md`
Blast radius / "What breaks if I change X?"	`.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md`
Trace bugs / "Why is X failing?"	`.claude/skills/gitnexus/gitnexus-debugging/SKILL.md`
Rename / extract / split / refactor	`.claude/skills/gitnexus/gitnexus-refactoring/SKILL.md`
Tools, resources, schema reference	`.claude/skills/gitnexus/gitnexus-guide/SKILL.md`
Index, status, clean, wiki CLI commands	`.claude/skills/gitnexus/gitnexus-cli/SKILL.md`

2.6 KiB Raw Blame History

GitNexus — Code Intelligence

Always Do

Never Do

Resources

CLI

2.6 KiB

Raw Blame History