14,111 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
You are a git rebase assistant. Your job is to rebase the current branch onto origin/ and intelligently resolve any merge conflicts that arise. The repository has already been fetched and the base branch is ; you may assume origin/ is up-to-date.
Opinionated GitHub-native development workflow with 51 skills for autonomous, issue-driven software development. Enforces TDD, strict typing, IPv6-first networking, comprehensive code review, local service testing, and continuous issue tracking. Features GitHub-based state management (no local state files)…
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODEOFCONDUCT, SECURITY, CHANGELOG, .gitignore…
Walk a code change (or full release branch) through a 12-item production-readiness checklist and produce a go / no-go report with concrete remediations.
Review GitHub pull requests using gh CLI and the GitHub API. Use when asked to review a PR, inspect PR changes, or choose approve/comment/request-changes.
Use this skill when you need to commit code changes with properly formatted commit messages that follow conventional commit standards. Use it when you have finished implementing a feature, fixed a bug, or have any other change ready to save. Produces fine-grained atomic commits with short imperative subjects and an…
Enrich an existing PKUP report directory — group commits into tasks, filter out non-creative groups, and write Polish descriptions. Use when the user has already generated a PKUP report and wants to clean it up or add "Zaprojektowałem..." descriptions.
Use this skill after a code PR is merged to integrate approved specs, update the retrospective with learnings, and clean up branches. It now automatically summarizes the retrospective file to keep it concise. Triggers include "integrate change", "post-merge cleanup", or completing a feature implementation.
Use 901 to run one feature end-to-end through SpecFlow's full pipeline as a single git-tracked run: high-level design, happy-path specs, scenario-by-scenario test-driven build-out validated and committed per module, cleanup, an optional expanded-coverage round, and a merge back to the base branch. Every design/spec…
Agent skill for interacting with code.storage (pierrecomputercompany), a managed Git infrastructure layer. Provides repository creation, branching, commits, file access, diffs, search, notes, GitHub sync, ephemeral branches, and forking through a REST HTTP API authenticated with customer-signed JWTs. Every repo…
Push the current branch to origin and ensure a PR exists for it (creating or updating one), with the symphony label applied. Use when the workflow says "push" or "open a PR".
Capture the intent behind staged changes as a provenance doc in docs/intents/, extracted from the Claude Code and Cursor chats that produced the code. Use when the user asks to generate or preview an intent doc, capture commit intent, check why the pre-commit intent hook skipped or failed, or run its self-test.
Claude Code skills and an orchestrator agent for declarative Harny workflows across Claude and Codex, including run analysis, PR delivery, and release management.
Semantic versioning enforcement: validates version bumps before commit/push/PR, supports multiple version files.
★not rated 11 todayA
tokens not measured
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: