A template-repository issue-handling workflow for investigating reports from consumer repositories, reproducing problems, identifying root causes, and proposing fixes. After approval, it updates the shared template files and runs tests.
A workflow for clarifying and recording pending requirements, technical debt, and bugs. Technical debt is work that should be done later to improve or correct a codebase.
A repository-cleanup tool for finding and removing clearly unwanted files, such as caches and operating-system or editor leftovers. It can preview proposed removals and protect files marked to keep.
A synchronization component for copying a repository template’s tools and template files into projects that use it. Its launcher ensures the latest version is copied before each synchronization.
A starting process for analysing and planning bug fixes. It covers reproducing the bug, finding its root cause, checking for similar problem areas, planning tests, and recording the result; it does not change production code.
A backlog-planning skill that turns user requirements into well-formed development tasks. A backlog is the list of work a team may do, usually ordered by priority.
A skill for merging completed task branches into the local main branch. A branch is a separate line of code changes; the main branch is the project's shared baseline.
A reporting template for recording problems brought into a project by a template repository. It covers technical bugs in scripts, skills, hooks, or template files, as well as workflows or conventions that do not fit the project.
2 4d agoA118 tokens
At most 3 mods per repository are shown here — the rest are on their repository pages: