A workflow for splitting coding tasks into separate Git worktrees and running independent work in parallel. A worktree is a separate working folder connected to the same Git repository; stacked work builds dependent changes in order.
A guided cleanup workflow for a local Git workspace after a GitHub pull request has been merged. A worktree is a separate working directory connected to a Git repository, and a tmux session is a persistent terminal session.
A guarded procedure for rewriting Git commit history with rebase. Rebase changes the order or base of commits, so the procedure requires checking the repository, getting approval, making a backup, and verifying the result.
A guarded procedure for using Git reset, a command that moves a branch back to an earlier commit and can discard uncommitted changes. It first considers safer alternatives such as restoring files or reverting a commit.
A review loop that repeatedly applies fixes and runs another review until selected findings are gone. It distinguishes required fixes from optional improvement suggestions.
An agent that gathers reports from several code reviewers and combines them into one result. It classifies findings as fixes or improvements but does not change the code.
A plugin containing several GitHub operation skills, used through GitHub's command-line tool. It covers investigating failed CI checks, fetching repositories, pushing changes, and creating pull requests.
A tool for investigating failed GitHub Actions runs, pull requests, and jobs. GitHub Actions is GitHub’s service for automatically building and testing code.
A fetch and pull helper for non-interactive Git sessions, such as CI or remote control sessions without a terminal for entering an SSH passphrase. It tests non-interactive SSH first and can fall back to HTTPS authentication through GitHub CLI.
A pull-request and merge-request creation workflow for software repositories. A pull request or merge request is a formal proposal to review and merge committed code into another branch.
A set of learning aids for understanding code and technical work, including quizzes, tutoring, and navigation help. It addresses the knowledge gaps that can arise when AI tools do much of the work.
A troubleshooting workflow for finding out why a Nix package was built locally instead of downloaded from a binary cache. A binary cache stores already-built packages, while Hydra is an automated build service for Nix projects.
A setup pattern for Nix development environments, using separate project and developer configuration files plus direnv and GitHub Actions. Nix is a tool for describing repeatable software environments.
A lookup workflow for finding the exact package, command, file, derivation, or input path in Nix's package store. Nix is a package manager, and a derivation is the recipe used to build a package.
A group of product-development skills for translating business needs into specifications, designs, completion criteria, and integrated documentation. It also includes a product-research agent.
A design-document writing skill for defining how a software feature should be built. It creates or revises a basic design document and links each planned function to a stated requirement.
A Japanese-language filter that rewrites technical material into plain explanations for business staff, without technical terms or implementation details.
A skill for creating or revising one project-wide Definition of Done: a document that states what must be true before work counts as complete. It separates checks that tools can verify from checks that a person must confirm.
A final documentation workflow that merges feature work documents into the project's main specifications and design documents, then removes the temporary work directory after approval.