Menu
Commit, push, and update PR with a clean workflow. Checks for out-of-scope files before committing.
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
Create a structured implementation plan for a feature request. Covers architecture, system design, module design, pattern selection, and milestone-based task planning with DoD. Use when the user describes a new feature, significant change, or multi-step implementation task.
Execute an implementation plan milestone-by-milestone. Reads the plan, reviews lessons, then implements tasks using agents for parallelizable work. Invoke with /scrum-implement <plan-file-path> or triggered when the user asks to implement/execute a plan.
Extract lessons from a retrospective and review skills/agents for improvements. Creates lesson files in ~/Claude/lessons/ and suggests concrete changes to scrum skills. Invoke with /scrum-lessons <retrospective-path> or after running /scrum-retro.
Generate a sprint retrospective from a plan file and tech lead feedback. Analyzes what was planned vs what was built, identifies root causes, and produces actionable takeaways. Invoke with /scrum-retro <plan-file-path> or triggered when the user asks to create a retrospective.
Temporal Python SDK (`temporalio`) patterns, determinism rules, error handling, and testing. Trigger: When writing Temporal workflows, activities, or workers in Python, or when the user mentions Temporal, durable workflows, or the Python SDK in the context of workflow orchestration. Activated when working on files importing `temporalio`, `@activity.defn`, `@workflow.defn`, in directories named `temporal_app/`, `workflows/`, `activities/`, or when user asks about Temporal concepts, determinism, replay, signals, or activity patterns.
Set up a new Python/Django project with uv, ruff, basedpyright, pre-commit hooks, Justfile, Docker Compose, and CI. Invoke when starting a new Python project or when asked to set up project tooling.
| name | commit |
| description | Commit, push, and update PR with a clean workflow. Checks for out-of-scope files before committing. |
| disable-model-invocation | true |
| argument-hint | ["optional commit message"] |
Follow these steps exactly in order.
Run git remote -v to list all configured remotes.
Remember the chosen remote for Steps 3 and 4.
Run git status and git diff --stat to see all changed files (staged + unstaged + untracked).
Determine which files are in scope (related to the current task/branch) and which are out of scope (unrelated changes, config tweaks, leftover experiments, etc.).
If there are any files that look out of scope, stop and ask the user explicitly what to do with each one:
Do NOT silently include or exclude files. Always confirm with the user when ambiguous.
Stage only the confirmed files. Write a concise commit message:
$ARGUMENTS is provided, use it as the commit messageCommit the changes.
Push the current branch to the remote. If no upstream is set, push with -u to set tracking.
Check if a PR already exists for this branch using gh pr view.
gh pr edit to reflect the current state of all changes on the branch (not just this commit). Use git log <base>..HEAD to review all commit messages on the branch.gh pr create.Use this format for the PR body — keep it focused on what changed, no test plans:
## Summary
- Bullet points describing the changes across all commits on the branch
- Focus on what was added/changed/removed and why
- Group related changes together
IMPORTANT rules for writing PR descriptions: