This directory contains GitHub-specific configuration for the PRD Skill repository, aligned with LightSpeed org-wide standards.
- branch-types.yml - Org-wide branch type definitions and PR template routing
- branch-labels.yml - Automatic label application based on branch type
- changelog-rules.yml - Changelog entry rules and formatting
- labels.yml - Canonical label definitions for issues and PRs
-
PULL_REQUEST_TEMPLATE/ - PR templates for different branch types
pr_feature.md- Feature and enhancement PRspr_task.md- Task-based workpr_chore.md- Maintenance and housekeepingpr_docs.md- Documentation updatespr_release.md- Release PRsconfig.yml- Template configuration
-
ISSUE_TEMPLATE/ - Issue templates for different issue types
03-feature.md- Feature requests02-bug.md- Bug reports08-chore.md- Chores and maintenance
The PRD Skill repository follows the org-wide branching strategy documented in: https://github.com/lightspeedwp/.github/blob/develop/docs/BRANCHING_STRATEGY.md
Use format: {type}/{scope}-{title}
Valid types include:
feat/— New featuresfix/— Bug fixesdocs/— Documentationtask/— Scoped workrefactor/— Code refactoringchore/— Maintenancetest/— Testingci/— CI/CD updates
Example: feat/comprehensive-test-suite
- Create a branch following naming conventions
- Make changes and write descriptive commit messages
- Open a PR - the appropriate template will be suggested based on branch type
- Ensure all checks pass
- Request review from code owners
- Once approved, squash-merge to
mainand delete the branch
Labels are automatically applied based on:
- Branch type (from branch-types.yml)
- File changes (from labeler.yml if present)
- Manual assignment by maintainers
All labels must be defined in labels.yml.