GPT-5 finding
Inconsistent status variable naming in article template vs. taxonomy/logging
lowmaintainabilitymedium
- skills/fork-release-tracker/SKILL.md:170-171
- skills/fork-release-tracker/SKILL.md:215-228
The article template references ${status_code}, but the rest of the spec names concrete status constants and the logging step prints a human-readable taxonomy. The variable name is not defined elsewhere, which can cause minor confusion for implementers.
Recommendation
Standardize on a single variable name (e.g., ${STATUS}) and define that it must be one of the taxonomy constants. Use the same in both the article and log templates.