codex-patches
Use this when updating the codex submodule or when patch files in codex-patches/ need to be added, regenerated, or repaired.
Script and automate repetitive tasks and workflows.
Use this when updating the codex submodule or when patch files in codex-patches/ need to be added, regenerated, or repaired.
Use for Bun file I/O: Bun.file, Bun.write, streams, directories, glob patterns, metadata.
Bun package manager commands (install, add, remove, update), workspaces, lockfiles, npm/yarn/pnpm migration. Use for dependency management with Bun.
Accept Spectr change proposals by converting tasks.md to tasks.jsonc without requiring the spectr binary. USE WHEN you're in a sandboxed or restricted execution context and spectr is not available in your path. DO NOT USE WHEN you need a lightweight alternative for task acceptance, but have the spectr binary available. DO NOT USE when you have the spectr binary available.
Creates comprehensive README files with templates for different project types. Use when creating README, project documentation, or getting started guides.
Analyzes and optimizes Dockerfiles to reduce image size, improve build time, and enhance security. Use when optimizing Docker images, reducing build times, or improving Dockerfile structure.
Execute specification-driven implementation with automatic quality gates, multi-agent orchestration, and progress tracking. Use when building features from specs, fixing bugs with test coverage, or refactoring with validation.
Generates conventional commit messages by analyzing git diffs and changes. Use when writing commit messages, following commit conventions, or documenting changes.
ไพ็ ง Keep a Changelog ๆ ผๅผๆฐๅไธ็ถญ่ญท CHANGELOG.mdใ ไฝฟ็จๆถๆบ๏ผๅปบ็ซๅๆดๆฅ่ชๆก็ฎใๅๅค็ผๅธใ่ฎฐๅฝๅๆดใ ๅ ณ้ตๅญ๏ผchangelog, release notes, CHANGELOG.md, keep a changelog, ๅๆดๆฅ่ช, ็ผๅธ่ฏดๆใ
ๅผๅฐ้ๆงๆฑบ็ญๅๅคง่ฆๆจก็จๅผ็ขผๆน้ฒใ ไฝฟ็จๆๆฉ๏ผ้ๆง็จๅผ็ขผใ้บ็็ณป็ตฑ็พไปฃๅใๆ่กๅตใ้ๅฏซๆฑบ็ญใ ้้ตๅญ๏ผrefactor, rewrite, legacy, strangler, technical debt, ้ๆง, ้ๅฏซ, ๆ่กๅต.
ๅผๅฐ้ๆงๅณ็ญๅๅคง่ฆๆจก็จๅบ็ ๆน่ฟใ ไฝฟ็จๆถๆบ๏ผ้ๆง็จๅบ็ ใ้บ็็ณป็ป็พไปฃๅใๆ่กๅตใ้ๅๅณ็ญใ ๅ ณ้ตๅญ๏ผrefactor, rewrite, legacy, strangler, technical debt, ้ๆง, ้ๅ, ๆ่กๅต.
ไพ็ ง Keep a Changelog ๆ ผๅผๆฐๅฏซ่็ถญ่ญท CHANGELOG.mdใ ไฝฟ็จๆๆฉ๏ผๅปบ็ซ่ฎๆดๆฅ่ชๆข็ฎใๆบๅ็ผๅธใ่จ้่ฎๆดใ ้้ตๅญ๏ผchangelog, release notes, CHANGELOG.md, keep a changelog, ่ฎๆดๆฅ่ช, ็ผๅธ่ชชๆใ
Write and maintain CHANGELOG.md following Keep a Changelog format. Use when: creating changelog entries, preparing releases, documenting changes. Keywords: changelog, release notes, CHANGELOG.md, keep a changelog, ่ฎๆดๆฅ่ช, ็ผๅธ่ชชๆ.
Guide refactoring decisions and large-scale code improvements. Use when: refactoring code, legacy modernization, technical debt, rewrite decisions. Keywords: refactor, rewrite, legacy, strangler, technical debt, ้ๆง, ้ๅฏซ, ๆ่กๅต.
Provides git workflow assistance, branch management, and commit message optimization
Systematic bug fixing workflow with regression tests and PR creation. Use when the user asks to "fix a bug", "debug an issue", "resolve a problem", or provides error messages/failing tests to fix. Handles reproduction, root cause analysis, test creation, fix implementation, and PR submission.
Git workflow standards - branch management, commit conventions, and PR creation process. Use when planning work that involves git operations or PR submissions.
Git commit guidelines for incremental commits. Read this when user asks you to auto commit as you go
When python, flask, or jinja are being written or edited.
Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.
Upgrades Kirby and maintains dependencies safely using composer audit, plugin compatibility checks, and official docs. Use when updating Kirby versions or making maintenance changes that affect runtime.
All modes that write scripts or code follow these app standards for communication, modularization, simplification, naming conventions