菜单
Commit each changed file individually with conventional commit messages, create a new feature branch, push, and open a PR. Used when the user wants fine-grained, file-level commits rather than squashing everything into one.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | granular-commits-pr |
| description | Commit each changed file individually with conventional commit messages, create a new feature branch, push, and open a PR. Used when the user wants fine-grained, file-level commits rather than squashing everything into one. |
| version | 1.0.0 |
| metadata | {"hermes":{"tags":["git","github","conventional-commits","pr-workflow"]}} |
Commits every modified/new/deleted file with its own conventional commit message, then creates a fresh feature branch, pushes, and opens a PR.
git status --short
Identify:
M — modified files?? — new (untracked) filesD — deleted filesFor modified/untracked files:
git add <path/to/file>
git commit -m "type(scope): description
Detailed body explaining the change."
For deleted files:
git rm <path/to/file>
git commit -m "type: description"
Conventional commit format:
feat: — new feature or modulefix: — bug fixrefactor: — code change that isn't a fix or featuretest: — test changesdocs: — documentationchore: — maintenance (deps, version bumps, lockfiles)Scope (optional, in parentheses): the module/area affected, e.g. refactor(tools):, test(conftest):
Body: 1-3 lines explaining WHY the change was made, not just what changed.
git log --oneline -N # N = number of commits just made
Confirm all files are committed:
git status --short # should be empty
Never reuse an existing branch. Name format: feat/<descriptive-kebab-case>
git checkout -b feat/v0.4.0-browser-refactor
git push origin feat/v0.4.0-browser-refactor
Use gh pr create with a structured body:
gh pr create \
--title "type: short summary of the release" \
--body "## Summary
One-paragraph overview.
## Changes
### Section 1
- bullet points
### Section 2
- bullet points
### Files
| File | Status |
|------|--------|
| path/to/file.py | Updated |
| old/file.py | Deleted |
| new/file.py | New |
N tests passing" \
--base main
feat/* branch, even if commits are already on another branch. Use git checkout -b from the current state.gh pr close <N> before opening the new one.fix: for bugs, feat: for new code, refactor: for rewrites, chore: for boring stuff.Maintain CHANGELOG.unreleased.md in psamvault-cli. When the user opens a PR with code changes, read the PR diff, write entries to the unreleased file, and open a separate PR for the changelog update so it merges cleanly alongside the code changes.
Guide new feature development from idea to build-ready plan: structured summary → multiple-choice questions → PLAN.md collaboration → handoff to plan and subagent-driven-development skills.
Publishes Python projects to TestPyPI and PyPI, then creates a GitHub version release. Use this skill when the user wants to publish, release, or ship a Python package, or asks to bump a version and push to PyPI. Requires a pyproject.toml in the project. Workflow: build -> TestPyPI -> user tests locally -> PyPI + GitHub release. Before the version bump, loads the granular-commits-pr skill to commit codebase changes individually. Also covers the post-release backup of the py-publish skill itself to the skills backup repo at C:\Users\USER\.copilot\skills (github.com/psam-717/skills).
Scans the current git repo for all untracked and modified files, examines their contents/diffs, generates meaningful commit messages, presents them to the user for verification, then stages and commits each file individually. After committing, optionally creates a new branch and opens a PR for major updates (seeks user approval first). Supports both interactive mode (user-confirmation required) and cron/ automated mode (no interaction, commits autonomously). Trigger phrases: "stage and commit", "commit my changes", "commit all files", "git commit", "commit my modified files", "create a commit message", "auto-commit cron job". Works on Windows (git-bash/PowerShell) and POSIX.
Performs a thorough, beginner-friendly breakdown of the entire current project. Reads every file in the codebase and produces an extensive explanation of what the project is, how it is structured, how data flows through it, and what every major piece of code does. Use this skill when asked to explain a project, walk through a codebase, give an overview of how something works, or onboard onto an unfamiliar repo.
Performs a thorough codebase review and debugging session. Scans all source files for bugs, security issues, logic errors, and code quality problems. Presents a full bug report to the user and waits for approval before making any changes. After approval, fixes only the approved bugs, then delivers a summary of every change made and a description of the application's current workflow. Use this skill when asked to review code, debug the codebase, find bugs, or audit code quality.