// Deploy AWS Lambdas using the guaranteed deploy scripts only. Never deploy via IAC (CDK). Requires AWS SSO login first. Use when deploying any AWS Lambda repo.
Per-repo commit worker. Analyzes ALL changed files independently, groups them by ticket, and makes MULTIPLE focused commits — one per logical group. Spawned in parallel by /pwf-commit-changes (one instance per repo). Never create branches or push.
Commit uncommitted changes across all workspace repos and tag commits with ticket numbers. Each repo gets its own subagent that analyzes files individually, groups them by ticket, and makes multiple focused commits. Use when the user pastes issue text (with TICKET-XXX) and wants to commit, or says "commit with these tickets" / "commit my changes".
Load and enforce mandatory project documentation baseline before implementation work.
Run standardized post-implementation documentation maintenance and quality checks.
Use when implementation is complete to close branch/worktree with a disciplined decision flow (merge, PR, keep, discard) plus cleanup.
Manages Git worktrees for isolated parallel development. Use when creating separate working directories for branches without switching the main repo.
| name | aws-lambda-deploy |
| description | Deploy AWS Lambdas using the guaranteed deploy scripts only. Never deploy via IAC (CDK). Requires AWS SSO login first. Use when deploying any AWS Lambda repo. |
Lambdas are deployed only via the project's deploy scripts, using AWS CLI. No CDK deploy, no IAC apply.
From the Lambda repo root, inspect ./scripts/ for guaranteed deploy scripts.
Preferred script names:
deploy-lambda-guaranteed.shdeploy-all-lambdas-guaranteed.shAccept equivalent variants only if they are clearly the same guaranteed flow.
Each Lambda repo that has deploy scripts must use them:
./scripts/deploy-lambda-guaranteed.sh <lambda-name> [--profile PROFILE] [--region REGION]./scripts/deploy-all-lambdas-guaranteed.sh [--profile PROFILE] [--region REGION]Script names may vary by repo (e.g. deploy-lambda-guaranteed.sh, deploy-all-lambdas-guaranteed.sh). Look in that repo's scripts/ folder.
If no guaranteed deploy script exists, do not deploy manually.
Instead, pause and ask the user before creating defaults. Use this message pattern:
No guaranteed deploy script was found in ./scripts. I suggest creating standard deploy scripts now (single Lambda and deploy-all), based on the plugin defaults. Should I create them for this repo?
If the user approves, create these files in the target Lambda repo:
./scripts/deploy-lambda-guaranteed.sh./scripts/deploy-all-lambdas-guaranteed.shTemplate source (inside plugin):
assets/lambda-deploy/deploy-lambda-guaranteed.template.shassets/lambda-deploy/deploy-all-lambdas-guaranteed.template.shAfter creation:
chmod +x).Before any AWS CLI command (including deploy):
aws sso login --profile <aws-profile>
Replace <aws-profile> with the project's AWS profile. If you skip this, deploy will fail with credential/session errors.
notification-processor, reply-suggestions-lambda):./scripts/deploy-lambda-guaranteed.sh <name> --profile <aws-profile> --region <region>The first argument is the Lambda package/name (e.g. notification-processor, appsync-publisher). Run the script with --help to see available names for that repo.
aws lambda update-function-code (or create if missing). Idempotent and safe to re-run.cdk deploy or any IAC to deploy Lambda code.