pr-workflow

SKILL.md

Guidelines for commits, pull requests, CI workflows, and secure dependency management.

Emphasizes atomic, focused commits with clear messages; recommends git rebase -i for clean history and avoiding mixed logic/formatting changes

PR best practices include keeping changes small and focused, running tests before submission, and using WIP states in GitHub Actions when needed

Security checklist: never commit .env files, credentials, or secrets

Dependency additions require a license file in licenses/ and an entry in NOTICE.md

External API/tool usage should rely on official documentation rather than guessing parameters

PR Workflow Guide

Commit Practices

Atomic commits. Small, focused, single purpose

Don't mix: logic + formatting, logic + refactoring

Good message = easy to write short description of intent

Learn git rebase -i for clean history.

PR Guidelines

Keep PRs focused and small

Run relevant tests before submitting

Each commit tells part of the story

CI Environment Notes