DJLS Changelog
SkillDocs & knowledgeUse when adding release notes, changelog entries, user-facing changes, internal changelog notes, or preparing a PR/release for django-language-server. Handles Keep a Changelog formatting and entry style.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the DJLS Changelog skill
What this skill tells your AI
The instructions your AI receives, as published by joshuadavidthomas/django-language-server in .agents/skills/djls-changelog/SKILL.md and read by ahel’s review.
Use this for any user-facing change or release-note work.
Rules
- Every user-facing change needs a changelog entry in the same commit or PR.
- Entries go under
[Unreleased]in the appropriate section:AddedChangedDeprecatedRemovedFixedSecurity
- Keep entries short and factual: what changed, not why.
- Use past tense verbs:
Added,Fixed,Removed,Bumped. - Prefix internal-only changes with
**Internal**:and list them after user-facing entries. - Backtick-wrap code identifiers: crate names, types, commands, config keys.
Example
### Fixed
- Fixed `{% load %}` completions for custom template tag libraries.
- **Internal**: Refactored `djls-semantic` validation helpers.
Signals
- GitHub stars
- 203
- Forks
- 10
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
djls-changelog- Source
- github.com/joshuadavidthomas/django-language-server