Comet: agent skill harness for turning ideas into evaluated workflows
About the project
Comet is a resumable workflow and skill platform for coding tasks, covering requirements work as well as skill creation, evaluation, and release. It supports separate Native and Classic workflows and can coordinate implementation and verification across isolated Git worktrees. The catalogue contains skills and instructions that implement Comet-related workflows.
A workflow for keeping Comet documentation in Chinese and English aligned across READMEs, skills, release notes, and website pages. It preserves confirmed wording, repository structure, examples, commands, links, and configuration names.
A workflow for diagnosing failed GitHub Actions checks on a Comet pull request. GitHub Actions runs automated builds and tests; a pull request is a proposed code change waiting to be reviewed and merged.
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.
A read-only workflow for checking and classifying Comet GitHub Issues, which are reports or requests about a software project. It compares each report with the repository’s code, tests, configuration, installation behavior, and existing issues.
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
A release-preparation workflow for Comet that uses the real version, branch history, and user-visible changes to prepare a changelog and release checks. A changelog is a dated record of what changed for people using the software.
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
A guided creator for building or upgrading Comet Classic workflow skills. It turns a user's description into a structured workflow that defines stages, responsibilities, required skills, outputs, checks, and handoffs.
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
A Comet workflow step for turning an approved design into an implementation plan and completed code changes. Comet is the project workflow system described by the add-on.
A workflow guide for turning an existing software change into a detailed technical design document. It builds on earlier proposal and design files and defines implementation risks, tests, and edge cases.
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
A workflow for managing Native changes in Comet, where requirements, progress, and acceptance results are saved in project files. It uses the Comet command-line runtime to move through defined work stages.
A guide for starting an OpenSpec change: a tracked software task with proposal, design, task, and state files. It also covers choosing or restoring the correct project workspace and output language.
A read-only review guide for checking the current Comet change, a managed software-change workflow. It focuses on correctness, security, and boundary problems without changing files or advancing the workflow.
A Comet workflow for small or medium changes that can be described as one OpenSpec change. OpenSpec is a specification-driven way to plan and apply software changes.
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: