A set of software engineering skills and an automated coding framework
Skill Claude CodeCodex
A code-and-test review skill that compares the current implementation and existing tests with an approved test-matrix CSV, a spreadsheet listing expected checks. It records whether each requirement is implemented and tested.
Skill Claude CodeCodex
A tool that turns the current conversation and project context into a product requirements document, or PRD—a plan describing a problem, solution, user needs, decisions, tests, and limits.
Skill Claude Code
A product-requirements writing skill that turns the current conversation into a business-focused specification for a product manager. It explains user situations, decisions, rules, stories, and page interactions in everyday language.
Skill Claude Code
A specification-writing skill that turns the current conversation and repository context into a technical product specification and publishes it to the project’s issue tracker. An issue tracker is a system for recording work items, such as GitHub Issues.
Skill Claude Code
A workflow for breaking a plan, specification, or conversation into small end-to-end work tickets, with each ticket stating which earlier tickets block it. A ticket tracker is a tool for recording and managing such work items.
Skill Claude Code
A triage workflow for sorting issue reports and, where configured, external pull requests. Triage means classifying a report, checking whether it has enough information, and deciding who should handle it next.
Skill Claude Code
A workflow for creating a GitHub Pull Request or GitLab Merge Request from a branch that has already been pushed. It checks the complete branch range and evidence, asks for confirmation, and then creates the request.
Skill Claude CodeCodex
A template and writing procedure for producing a Pull Request or Merge Request description. It summarizes the change, supporting evidence, and risks for human reviewers without creating or merging the request.
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: