Complete makefile toolkit with generation and validation capabilities
97
97%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
{
"context": "Tests that the agent follows the legacy conversion workflow: validate current state, fix issues, apply formatting, add .PHONY, and re-validate. Also checks that .DELETE_ON_ERROR and tab indentation are addressed.",
"type": "weighted_checklist",
"checklist": [
{
"name": ".PHONY added",
"description": "The modernized Makefile includes a .PHONY declaration covering at least 'all', 'test', 'clean', and 'install'",
"max_score": 20
},
{
"name": ".PHONY issue explained",
"description": "modernization-notes.md explains that 'make clean' silently did nothing on machines with a file named 'clean', caused by missing .PHONY",
"max_score": 10
},
{
"name": "Tab indentation present",
"description": "Recipe lines in the modernized Makefile start with hard tab characters (the input used spaces/inconsistent indentation)",
"max_score": 15
},
{
"name": "Validation step documented",
"description": "modernization-notes.md describes running a validation step (make -n, validate_makefile.sh, or mbake) on the original Makefile before making changes",
"max_score": 10
},
{
"name": ".DELETE_ON_ERROR added",
"description": "The modernized Makefile includes .DELETE_ON_ERROR to clean up partial output files on failure",
"max_score": 15
},
{
"name": "Re-validation documented",
"description": "modernization-notes.md documents that the modernized Makefile was re-validated after changes",
"max_score": 10
},
{
"name": "Format step mentioned",
"description": "modernization-notes.md mentions using mbake format or equivalent formatting step as part of the modernization process",
"max_score": 10
},
{
"name": "Changes enumerated",
"description": "modernization-notes.md lists each specific change made (not just a generic summary)",
"max_score": 10
}
]
}