coding.fix_constants
SkillDev toolsMove constants to their appropriate scope based on usage
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the coding.fix_constants skill
What this skill tells your AI
The instructions your AI receives, as published by causify-ai/helpers in .claude/skills/coding.fix_constants/SKILL.md and read by ahel’s review.
Move constants to match their usage scope and visibility requirements. Constants should be placed where they are used and made private when not part of the module's public interface
Conventions
- Follow the section
# Constantsfrom the file.claude/skills/coding.rules.md
Apply the conventions in .claude/skills/coding.rules.md when writing constant
definitions and names
Verification
- Confirm each constant sits in the smallest scope that uses it (local, module-private, or module-public)
- Confirm module-private constants are prefixed with
_
Signals
- GitHub stars
- 145
- Forks
- 160
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
coding-fix-constants- Source
- github.com/causify-ai/helpers