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 commit sorting within groups. It focuses on proper usage of the package's sorting options and APIs.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses writeChangelogString",
"description": "Uses the writeChangelogString function from conventional-changelog-writer to generate the changelog from commits.",
"max_score": 20
},
{
"name": "Implements commitsSort option",
"description": "Uses the commitsSort option in the Options parameter to control how commits are sorted within groups.",
"max_score": 25
},
{
"name": "String-based sorting",
"description": "Implements sorting by property name (string) for simple sorting cases (e.g., commitsSort: 'hash' or commitsSort: 'header').",
"max_score": 15
},
{
"name": "Array-based multi-level sorting",
"description": "Implements multi-level sorting using an array of property names (e.g., commitsSort: ['scope', 'subject']).",
"max_score": 15
},
{
"name": "Function-based custom sorting",
"description": "Implements custom sorting by providing a comparator function to commitsSort (e.g., commitsSort: (a, b) => ...).",
"max_score": 15
},
{
"name": "Passes options correctly",
"description": "Correctly passes the Options object as the third parameter to writeChangelogString, ensuring sorting configuration is applied.",
"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