A workflow for splitting a large task into separate Linear issues, where Linear is a project-management tool for tracking development work. It creates a project and represents dependencies with blocked-by links rather than parent and child issues.
A review workflow for plan files, which are written outlines of planned development work, using the Codex command-line tool. It checks whether the plan matches the current discussion, decisions, requirements, and risks.
A process for reviewing code changes with the Codex command-line tool. It compares the changes with the repository's default branch and checks them against the saved work plan.
A process for starting implementation from the newest saved work plan. It turns the plan's execution steps into tasks, completes them in order, creates a commit for each task, and finishes with a review.
A rule set for replacing GitHub Actions version tags with fixed commit references. GitHub Actions are automated steps that run in a repository, while a commit reference identifies one exact version of an action.
A process for assigning coding tasks to Cursor Cloud Agent, a remote coding agent, and then monitoring its work. It can also check pull requests and connect work to Linear, a project-tracking tool.
A set of rules for creating clear, reviewable work plans. It records the goal, scope, approach, tests, risks, and the user's original words when needed.
A way to read Notion pages and documents as Markdown, including pages found from a Notion link or by searching Notion. Notion is a workspace for storing notes and team documents.
A handoff rule for sending a task from the Devin command-line tool to Devin Cloud and asking Devin Cloud to give the coding work to Cursor Cloud Agent.
A safeguard for gcloud and bq commands when Google Cloud authentication has expired. gcloud is Google's command-line tool, and bq is the command-line tool for BigQuery, a cloud data warehouse.
A workflow for updating a GitHub pull request’s title and description after reviewing the branch changes and commit history. It requires the description to be written in Japanese and follows project-specific rules.
A controlled way to create or update development diary entries in esa, a team documentation service. It uses a fixed local YAML file and requires diary content to be organized with bullet points.
A format for keeping an internal record of investigations, including sources, commands, queries, results, and unanswered questions. It stores this record separately from polished documents for users.
★not rated 11 2mo agoA115 tokens
originalMIT
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: