A coding skill for adding or improving comments and documentation comments in source code, including JSDoc and docstrings. It records how code fits into its package, service, callers, and dependencies without changing the implementation.
A workflow for sending locally changed coding skills to an approved upstream GitHub repository as a pull request, a proposed change for its maintainers to review.
A skill for creating Git commits using Conventional Commits, a standard format for describing changes. It infers the commit type and scope from staged changes, checks for breaking changes and secrets, and requires pre-commit hooks to run.
A tool for turning requirements into a structured GitHub Issue tree: a tracking issue, phase issues, and smaller child issues. GitHub Issues are records for planning and tracking work, and phases group related tasks.
A GitHub issue creator that can split a larger task into a parent issue and linked sub-issues. It uses the GitHub command-line tools to create and connect them.
A GitHub pull-request creator that uses the Conventional Commits format and includes a security check based on the OWASP Top 10. A pull request is a proposed set of code changes for review; Conventional Commits is a standard way to label changes.
A GitHub Issue implementation workflow that creates a detailed plan in /local-plans/ before writing code. After approval, it implements the issue, checks security risks, runs tests, and makes a Conventional Commit.
A GitHub pull-request review skill. It checks continuous-integration results, code quality, common web security risks from the OWASP Top 10, and Conventional Commits formatting.
A read-only code review process for checking a code change against quality, architecture, and OWASP Top 10 security guidance. The OWASP Top 10 is a commonly used list of major web-application security risks.
A setup workflow that creates Claude Code configuration in a repository, including instructions, agents, rules, skills, and hooks—automatic actions run at defined points.
A tool for creating project items in bulk from Markdown checklists, YAML task lists, or requirements documents. It reads fields such as title, details, priority, and size, then adds them to a GitHub project.
A tool for archiving GitHub project items whose status is Done. Archiving removes completed items from the active project view while keeping them in the project’s history.
A tool for converting draft items in a GitHub Project into real GitHub Issues, while carrying over fields such as status, priority, and size. It can also attach issues as sub-issues under a selected or newly created parent issue.
A setup guide for creating a GitHub Project v2, GitHub’s board for tracking repository work, with standard Status, Priority, and Size fields. It uses the GitHub website rather than the command line.
A skill for synchronizing GitHub issue or pull-request states with project-board Status values. It can create a workflow for automatic synchronization or correct existing mismatches in bulk.
A skill for filtering project items and updating selected fields in bulk. It supports text, number, date, and single-select fields such as status, priority, and size.
A read-only reporting tool for GitHub projects. It counts and summarises items by status, priority, and size, and reports completion rates and the priority breakdown of unfinished work.
A skill for adding repository safeguards, including continuous-integration checks, review guidance, required-check jobs, and branch-protection rules. Continuous integration, or CI, automatically checks code changes before they are merged.
A maintenance tool for an existing .claude setup, including its instructions, helper agents, rules, skills, and hooks. It compares the setup with a desired structure and proposes additions after asking for approval.
A documentation updater for repositories that use CLAUDE.md, a file containing instructions and project information for Claude coding tools. It updates the skill list and repository structure from changes since the last tracked update.
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: