A code-review workflow that produces two separate reviews: one checks coding standards and another checks whether the implementation matches the stated specification. A specification is the agreed description of what a change must do.
A software-development workflow coordinator that routes a request through the needed stages, from clarifying the work and writing requirements to planning tasks, coding, and review.
A planning aid that turns an approved product requirements document (PRD) into small, independent tasks. Each task covers the complete path from data to storage and testing.
A method for turning the current conversation into a product requirements document (PRD), which records a feature's goal, scope, testable boundaries, constraints, and risks.
A planning method for large DevOps migrations or refactors that cannot be completed in one work session. It keeps a map of research, prototype, design-review, and implementation tickets, then selects one available ticket at a time.
A background checker for CHANGELOG files, which record what changed between software releases. It applies Keep a Changelog categories and Semantic Versioning, a standard for choosing version numbers based on the kind of change.
A process for managing a feature branch that remains open for more than two days. A feature branch is a separate line of code changes used to develop work before merging it into the main codebase.
A Git branch planning guide for starting a coding task. A branch is a separate line of work in a Git project, so changes can be developed without changing the main code directly.
A Git safety guard that watches work in a Git repository and intercepts commands that could cause hard-to-recover changes. Git is the system used to track code history and branches.
A capture procedure for saving web pages, ideas, and clipped messages as Markdown notes in an Obsidian inbox. Obsidian is a note-taking app that stores plain-text Markdown files.
A note-classification skill for deciding which subject area or project an inbox note belongs to. Notes that cannot be assigned confidently are marked for later review.
A tool for checking an entire Obsidian knowledge base and improving the links between its notes. It finds groups that may need an index note, called a MOC, and larger groups that may benefit from a combined hub note.
A note-refinement tool for notes that have already been organized into a subject folder. It progressively adds bold text, highlights key quotations, and writes a short action summary; it can also detect when related notes may need combining.
A writing-stage router for turning prepared notes into finished text. It chooses whether to use steps for collecting fragments, organising beats, shaping sections, and editing an article.
A coordinator for managing all content in an Obsidian vault, a folder of linked Markdown notes. It guides notes from capture and sorting through summarising, writing, and linking.
An Obsidian note-organization workflow that moves a classified note into a domain or project folder, updates its metadata and tags, and checks whether a topic index should be created. Obsidian is a note-taking app that stores linked Markdown files.
A method for studying one important concept in depth after it has been identified on a subject map. It gathers focused material, answers what the concept is and how it relates to others, then updates the map.
A note-making step that turns a completed learning map and concept understanding into organised notes in an Obsidian inbox for later knowledge management.
A learning workflow for understanding an unfamiliar subject from the ground up by mapping its concepts, studying selected parts, checking the evidence, and updating the map.
A method for building a map of an unfamiliar subject from reading materials. It collects sources, extracts and groups concepts, connects them by meaning, and creates a list of topics to study more deeply.
A fact-checking procedure for learning conclusions that compares trusted sources, records disagreements, and separates facts from opinions and guesses.
A project wrap-up procedure that extracts reusable lessons before moving completed or replaced project files into an archive.
★not rated 2 2mo agoA34 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: