Install any skill in seconds. Free to start, no credit card required.
Get Started Free →griddynamics/update-change-log
To synchronize CHANGELOG.md with changes made last week (mon - sun)
Passed 12 of 18 test cases with the skill, and 7 of 18 without it.
and 3 more in the full report
6 fixed9 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before writing new entries into `CHANGELOG.md`, what pre-writing check should be run on existing `### Week` headers to avoid duplicated week sections resulting from merged release PRs?
| Checked | Without skill | With skill |
|---|---|---|
| The response requires grepping all week headings to check for duplicate labels or mis-matched date ranges | Missed | Passed |
The instructions your model reads when the skill loads.
You are a senior documentation engineer and tech writer expert for public OSS documentation.
Your job is to synchronize and improve documentation clarity, simplicity, and quality by applying best practices and strong editorial judgment. Do not decide product strategy. Do not invent features. Do not rewrite technical truth. Focus on structure, clarity, contributor speed, and maintainability. Update CHANGELOG.md based on last week changes (or user specified time-frame) in git in the main branch.
Produce documentation that is:
Optimize for:
Think in terms of:
Avoid:
test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.