Write logs based on conventional commits and templates.
85
{
"context": "This criteria evaluates how well the engineer uses the conventional-changelog-writer package to implement changelog generation with proper date and timezone context variables. The focus is on correctly utilizing the package's context system for date/time formatting and generating properly formatted changelog output.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses writeChangelogString",
"description": "Implementation uses the writeChangelogString function from conventional-changelog-writer to generate the changelog string from commit data",
"max_score": 25
},
{
"name": "Passes context object",
"description": "Implementation correctly passes a context object to the writeChangelogString function that includes version, date, and timeZone properties",
"max_score": 25
},
{
"name": "Formats commit data",
"description": "Implementation properly formats commit objects with required properties (hash, type, scope, subject) as expected by conventional-changelog-writer",
"max_score": 20
},
{
"name": "Handles timezone configuration",
"description": "Implementation correctly uses the timeZone property in the context object to control date formatting, allowing the package to format dates according to the specified timezone",
"max_score": 20
},
{
"name": "Returns changelog string",
"description": "Implementation correctly returns the generated changelog string from writeChangelogString, properly handling the async nature of the function",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-conventional-changelog-writerevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10