Menu
Commit and push changes with exclusions and a generated commit message
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build a step-by-step path from a plain repository to a full agent-driven engineering workflow. Inspects the repo first to detect the full tech stack, package managers, CI systems, and monorepo layout before making any changes. Then initializes APM, sets up spec-driven development (OpenSpec by default, or respects existing systems like SpecKit and BMAD), adds deterministic checks matched to the detected stack, installs applicable AI skills, creates workflow documentation, configures AI IDEs (Copilot, Cursor, Windsurf, Claude Code, OpenCode), and verifies the entire setup.
Evaluate and score how AI-native a repository is. Checks for the existence and maturity of AI primitives -- spec-driven development, deterministic checks, AI skills, documentation, IDE configuration, and agentic legibility -- and produces a scored markdown report with prioritized recommended actions.
Stack-aware code review orchestrator that detects tech stacks from changed files, dispatches parallel review lanes to subagents with prescriptive instructions, synthesizes findings, and runs a fix loop for deterministic fixes. Supports TypeScript/JavaScript, Python, and Java.
Monitor a GitHub pull request after creation, wait for new review comments, resolve code review comments after fixes, and report CI success or failure. Use when the user wants the backend of the review flow handled after a PR is opened.
Create a pull request with automatically recommended reviewers based on git history. Use this skill when the user wants to create a PR with reviewers, open a pull request, or submit changes for review with the right people assigned.
Use for workflows that fetch GitHub pull request review comments with the gh CLI, identify Copilot review threads, and resolve them after code changes. Trigger when asked to review/resolve Copilot PR comments, fetch PR review threads, or document how to close review threads via gh api graphql.
| name | commit-and-push-changes |
| description | Commit and push changes with exclusions and a generated commit message |
| compatibility | Requires git to be installed |
| metadata | {"version":"1.0"} |
Commit all changes except specified files, with an auto-generated or user-provided commit message.
Step 1: Show the current state of changes:
git status --short
Step 2: Identify files to exclude from the commit.
Always exclude:
.cursor/ foldersAPM and OpenSpec deployed content:
Repos using APM or OpenSpec will have deployed content under .github/ (e.g., .github/skills/, .github/prompts/, .github/instructions/, .github/agents/, .github/hooks/) and possibly .claude/. These files should be committed so that every contributor and Copilot on github.com gets agent context without running apm install. Only apm_modules/ should be gitignored.
If apm install was run during this session and new deployed files appeared, include them in the commit. If deployed files appear in git status but were not expected, run apm install to verify they are in sync with apm.yml before committing.
To detect unintended modifications, compare the changed files against the conversation history. If a file appears in git status but was not edited during this session, treat it as potentially unintended. For APM/OpenSpec-managed repos, keep .github/ and .claude/ changes that come from apm install and only exclude .github/ files that are still unexpected after re-running apm install. For non-APM repos, exclude unexpected .github/ files that are clearly out of scope for this task.
Step 3: Stage only the files we intentionally modified:
git add <file1> <file2> ...
Do NOT use git add -A or git add . as this will stage unintended files.
Step 4: Generate the commit message.
git branch --show-current | grep -oE '[A-Z]{2,}-[0-9]+'
git log --oneline -10 | grep -oE '[A-Z]{2,}-[0-9]+' | head -1
If no Jira key is found, ask the user for the story key. If the user confirms no Jira key is needed, proceed without one.
Generate the descriptive message based on the work done during this session (from conversation context), not from parsing git diff output.
Compose the final message in this format:
# With Jira key:
<JIRA-KEY>: <descriptive message>
# Without Jira key (when user confirms none is needed):
<type>: <descriptive message>
Where <type> is one of: feat, fix, refactor, docs, chore, test, ci.
Step 5: Present the commit details for confirmation:
📝 Commit Preview
Files to commit:
- file1.py
- file2.py
Excluded files (auto):
- .cursor/* (IDE configuration)
- package-lock.json (not modified by us)
Commit message:
EADL-1234: Add retry logic with exponential backoff
Proceed with commit? [Y/n]
Step 6: After user confirms, create the commit and push:
git commit -m "<COMMIT_MESSAGE>"
git push
Step 7: Show the result:
git log -1 --oneline