Write logs based on conventional commits and templates.
85
{
"context": "This evaluation assesses how effectively the engineer uses the conventional-changelog-writer package to implement an async generator-based changelog generation system. The focus is on proper usage of the writeChangelog function and its configuration options.",
"type": "weighted_checklist",
"checklist": [
{
"name": "writeChangelog usage",
"description": "Uses the writeChangelog function from conventional-changelog-writer to create the async generator functionality",
"max_score": 30
},
{
"name": "Async generator pattern",
"description": "Returns an async generator that properly yields changelog entries by invoking the function returned by writeChangelog with the commits parameter",
"max_score": 25
},
{
"name": "Context parameter handling",
"description": "Correctly passes the context object (with version, date, repository, host, owner) as the first parameter to writeChangelog",
"max_score": 15
},
{
"name": "Options parameter handling",
"description": "Correctly passes the options object (with groupBy, commitsSort) as the second parameter to writeChangelog",
"max_score": 15
},
{
"name": "Input type support",
"description": "The implementation correctly handles both Iterable<Commit> and AsyncIterable<Commit> as inputs (writeChangelog natively supports both)",
"max_score": 10
},
{
"name": "Commit interface alignment",
"description": "Uses or extends the CommitKnownProps type from conventional-changelog-writer or defines a compatible Commit interface matching the package's expected structure",
"max_score": 5
}
]
}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