A structured process for fixing software bugs, including reproducing the problem, finding its root cause, and writing a test that prevents it from returning. A regression test is an automated check that catches a previously fixed problem.
A workflow for updating CHANGELOG.md, the file that records what changed between software releases, using the Keep a Changelog format. It classifies changes such as new features, fixes, removals, and security updates.
A step-by-step process for reviewing a pull request or merge request, which is a proposed code change awaiting review. It combines file and change summaries, automated checks, and architecture review.
A broad code review guide that checks source code for quality, security, performance, and common development practices. It can review files, folders, features, recent changes, or a pull request—a proposed change submitted for review.
A code-organization guide based on Domain-Driven Design, an approach that keeps business rules separate from application actions, outside systems, and user interfaces. It also separates data-access code from the rest of the application.
A pre-commit workflow that coordinates updates to project memory, documentation, changelogs, roadmaps, architecture notes, and commit messages before code is saved to Git.
A checkpoint process that copies important project context into Memory Bank files before a conversation is summarized. It records current work, completed and upcoming tasks, decisions, and architecture changes.
A method for maintaining project notes in a set of Memory Bank files, including current context, progress, and important decisions. The notes preserve project state between conversations.
A project-starting workflow that creates a new application from an existing template and copies its rules, directory structure, skills, and working notes.
A process for keeping English and Traditional Chinese README files aligned. English is treated as the primary version, while the Chinese version mirrors its structure, links, terminology, and code examples.
A README maintenance workflow that keeps a project’s main introduction and usage guide aligned with code changes. README files usually explain installation, features, usage, settings, and project structure.
A release-preparation workflow for software projects. It covers checks before publishing, version-number updates, changelog and documentation updates, and deployment checks.
A tool that updates ROADMAP.md, a project file listing completed, ongoing, and planned work. It matches finished features to roadmap entries and changes their status.
A generator for new skills, meaning reusable instructions that guide an assistant through a particular task. It creates a standard folder and instruction-file structure with metadata such as the skill name, triggers, category, and supported tools.
A health-check tool for project instructions and coding-agent skills. It checks whether skill files, configuration instructions, chat modes, and project rules exist, agree with one another, and are up to date.
A test-suite generation workflow for software projects. It includes static checks, unit tests, integration tests, end-to-end tests, coverage reports, type checking, linting, security scanning, and dead-code detection.
★not rated 3 6mo agoA98 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: