bmorphism-stars
bmorphism's GitHub stars (2155 repos) and created repos - a curated index
bmorphism's GitHub stars (2155 repos) and created repos - a curated index
Create changesets for package changes in pull requests. Use whenever you modify code in any package (packages/*). Required before committing changes to packages. Handles versioning with patch for bug fixes, minor for features, and major only when explicitly requested.
Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not performative agreement or blind implementation.
Commit staged changes only using Conventional Commit parameters (validates inputs).
Validate code, commit, push, and create PR if needed
Use to spawn isolated worker processes for autonomous issue work. Creates git worktrees, constructs worker prompts, and handles worker lifecycle.
Generate new Nix configuration modules following the repository's standard pattern. Creates module boilerplate in system/, darwin/, or home/ directories with proper options structure, imports parent default.nix automatically, and follows best practices for module organization.
Guide for using GitHub MCP tools for repository operations. Use this when working with GitHub repositories, releases, tags, or branches.
Pulls latest changes from remote with conflict resolution. Use when: user wants to pull, fetch changes, or update from remote.
Build a compact, high-signal context brief (files, symbols, recent commits) instead of pasting large code blocks
Use when starting work - guidelines for asking questions and commit policies
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
Analyzes current git status and work in progress. Use when: user wants to understand current state, check work status, or see what's changed.
Fetches a GitHub issue, implements the fix, and verifies it. Use when: user wants to fix an issue, implement issue changes, or resolve a bug.
Verify implementation status by scanning local Git repositories for code, tests, and commit history. Use when checking if a feature is actually implemented.
Manages release-please PR merging workflow for monorepos. Handles batch merging, conflict resolution through PR closure/recreation, and iterative processing until all PRs are merged. Use when merging release PRs, handling PR conflicts, or managing release automation in monorepos.
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
Comprehensive guide for working with GitHub data and APIs. Use when fetching issues, PRs, discussions, comments, reviews, or any GitHub content. Covers tool selection (mcp_github vs fetch vs semantic search), complete conversation fetching patterns, pagination handling, and common workflows. Critical for avoiding standard API failures when fetching comments/reviews—MCP tools required.
Create or update GitHub issue for the story and sub-issues for tasks
Generate semantic commit messages following conventional commit format for agentconfig.org. Use when creating commits, reviewing staged changes, or when the user asks for help with commit messages.