From github
Validates repository state, runs lint/test/build/security checks, and enforces commit message standards with conventional commits formatting before PR submission.
How this command is triggered — by the user, by Claude, or both
Slash command
/github:requirementscreate-pr/references/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Requirements ## Repository and Authentication - Ensure the repository is clean, authenticated, and ready for PR submission. - Complete lint, test, build, and security checks before creating the PR. - Link related issues and apply accurate labels for traceability. ## Commit Message Standards - **Use atomic commits for logical units of work**: Each commit should represent one complete, cohesive change. - Title: entirely lowercase, <50 chars, imperative mood (e.g., "add", "fix", "update"), conventional commits format (feat:, fix:, docs:, refactor:, test:, chore:) - Scope (optional): lo...
3plugins reuse this command
First indexed Feb 16, 2026
npx claudepluginhub fradser/dotclaude --plugin github/commitCreates conventional commits with automatic type/scope detection, branch protection enforcement, and secret scanning. Accepts optional message or type scope message arguments.
/git-workflowOrchestrates git workflow from code review and quality gates through commit, push, and PR creation to target branch. Supports flags: --skip-tests, --draft-pr, --no-push, --squash, --conventional, --trunk-based.
/commitDisplays detailed guidelines and step-by-step process for writing high-quality Git commit messages, including analysis, regression checks, and formatting rules.
/commitCreates Conventional Commits with scope detection, co-author support, and pre-commit validation. Generates 'why'-focused messages from staged changes, blocking secrets or generated-only files.
/requirementsGenerates comprehensive business and technical requirements for a project, drawing from stakeholder analysis, architecture principles, risk register, and business case. Outputs suitable for vendor RFPs and architecture reviews.
/requirementsGenerates structured requirements for the active spec. Runs an adaptive interview (skippable with --quick), scopes the work, then delegates requirement writing to the product-manager subagent.