القائمة
Add a new version entry to CHANGELOG.md, or restructure the entire file, following the Keep a Changelog format and Semantic Versioning.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use this skill whenever an agent needs to query Go package/module metadata from pkg.go.dev. Triggers include: looking up Go package info, finding module versions, searching for Go packages, listing package symbols (types/functions/methods), checking what packages import a given package, checking for vulnerabilities in Go modules, or any task requiring structured data about the Go ecosystem. Also use when the user asks to "find a Go package", "check the latest version of a Go module", "look up Go API docs programmatically", or wants to build a tool that integrates with pkg.go.dev. Always use this skill rather than web-scraping or guessing at Go package metadata.
Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, multi-scope commits, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
استنادا إلى تصنيف SOC المهني
| name | keep-a-changelog |
| description | Add a new version entry to CHANGELOG.md, or restructure the entire file, following the Keep a Changelog format and Semantic Versioning. |
Use this skill when the user wants to add a new version entry to a CHANGELOG.md, or restructure the entire changelog file following the Keep a Changelog format and Semantic Versioning guidelines.
CHANGELOG.md to identify the last released version and its date.git log --oneline <last-tag>..HEAD to list all commits since that tag. If no tag exists for the last version, use git log --oneline and filter manually.date +%Y-%m-%d to get today's release date — never hardcode or guess it.CHANGELOG.md and note all existing version blocks.date +%Y-%m-%d and confirm the latest version date is still accurate.# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [X.Y.Z] - YYYY-MM-DD
### Added
- ...
### Changed
- ...
### Fixed
- ...
Omit any section that has no entries. Do not add empty sections.
Use only these standard Keep a Changelog section names, in this order when multiple sections are present:
| Section | When to use |
|---|---|
| Added | New features or capabilities |
| Changed | Changes to existing behavior |
| Deprecated | Features marked for future removal |
| Removed | Features removed in this release |
| Fixed | Bug fixes |
| Security | Security-related fixes or improvements |
feat: / add / new → Addedrefactor: / change / rename / move / update / improve → Changedfix: / bug / patch → Fixedremove: / delete / drop → Removeddeprecate: → Deprecatedsecurity: / cve / vuln → Securitydocs: / chore: / ci: / test: → Omit unless user-facing.When a commit message is ambiguous, infer intent from the diff or file name.
Add retry logic for HTTP requests