A code-documentation aid that adds or strengthens comments, JSDoc, and docstrings without changing the implementation. JSDoc and docstrings are structured notes that explain code for people and tools.
A workflow for contributing locally changed skills to their upstream Git repositories. An upstream repository is the project where the original skill is maintained.
A commit helper that creates Git commits using the Conventional Commits format, which labels changes such as features, fixes, or breaking changes. It examines staged changes and checks for breaking changes and accidentally included secrets such as .env files.
A skill for creating a hierarchy of GitHub Issues divided into phases. GitHub Issues are trackable work items; the skill creates a root tracking issue, phase issues, child tasks, labels, and links between them.
A tool for creating GitHub Issues and linking them into parent-and-child task groups. GitHub Issues are work items used to track bugs, features, and other tasks.
A skill for creating detailed implementation plans in Markdown files under /local-plans/. It first examines the codebase and organises work into verifiable steps.
A tool for creating GitHub pull requests, which propose code changes for review and merging. It prepares a Conventional Commits-style request with a summary, test plan, and design information, after an OWASP Top 10 security check.
An automation skill for implementing a parent issue's smaller, related issues in dependency order. It uses separate worktrees, which are independent working copies of a code repository, and handles the development workflow through merge readiness.
A reviewer for GitHub pull requests, which are proposed code changes, checking automated test results, code quality, common security risks, and commit-message conventions.
A read-only reviewer for local code changes, such as a Git diff, which shows edits between versions. It checks code quality, architectural fit, and common security risks.
A setup for adding Claude Code configuration to a repository, including instructions, agents, rules, skills, and hooks. Claude Code is a coding assistant that works inside a project.
A tool for turning Markdown checklists, YAML task lists, or requirements documents into project items. Each item can include a title, description, priority, and size.
A project-cleanup tool that archives project items whose status is Done. Archiving removes completed items from the active project view while retaining them for reference.
A guide for converting draft items in a GitHub Project into real GitHub Issues, which are trackable work items. It can preserve field values and link issues as sub-issues under a parent issue.
A guide for creating a GitHub Project, a board for organising repository work, with standard Status, Priority, and Size fields. It uses GitHub’s web interface and links the project to a repository.
A GitHub automation setup for keeping issue, pull request, and project-board statuses in sync. A pull request is a proposed code change submitted for review.
A project-management tool that changes fields on many project items at once. It supports fields such as status, priority, size, text, number, and date.
A read-only project progress report grouped by status, priority, or size. It includes the completion rate and a table showing the priorities of unfinished items.
A review and update tool for an existing Claude Code setup, including its instructions, agents, rules, skills, and hooks. It shows gaps and suggests changes for approval before adding them.
A documentation updater that keeps a repository’s CLAUDE.md file aligned with recent changes. It tracks the last update and refreshes the skill list and repository structure tree.
A skill for reviewing and updating an existing GitHub Issue tree, a hierarchy of related tracking issues and subissues. It recursively retrieves the tree and synchronizes its phases, labels, and summary sections.