Create commits tagged with [skip-cd] for non-deploy file changes.
npx skills add https://github.com/minorun365/marp-agent --skill commit-docs-minorun365
Please help me install this Agent Skill. Skill: commit-docs Source: https://github.com/minorun365/marp-agent/tree/main/.agents/skills/commit-docs Command: npx skills add https://github.com/minorun365/marp-agent --skill commit-docs-minorun365
Commits that only change documentation, editor settings, or other non-deploy files can trigger unnecessary Amplify builds and consume time and resources; this Skill helps avoid those redundant deployments by creating commits annotated to skip CI/CD.
Use the commit-docs skill to create a [skip-cd] commit for documentation and config updates by detecting non-deploy file changes, staging them, and committing with a message like "Docs update [skip-cd]".
High-intent search queries and answers about installing and using this skill.
To skip Amplify deployments for non-deploy changes, you can create commits tagged with [skip-cd]. The skill detects modified files, filters out deployment-sensitive paths, stages eligible files, and commits with a [skip-cd] appended message.
A skip-cd commit works by appending the [skip-cd] tag to your commit message, which signals the Amplify CI/CD pipeline to bypass the build process. This prevents unnecessary deployments when only non-critical files are changed.
You should not use a skip-cd commit for src, amplify, or package.json modifications. The skill detects these deployment-sensitive paths, emits warnings, and requires confirmation to prevent accidentally skipping required builds.
The best way to commit editor config changes without triggering a build is to stage only safe files and use a commit message appended with [skip-cd]. This targets non-deploy file updates specifically to bypass CI/CD.
Files considered safe for a skip-cd commit include documentation, editor settings, and metadata. The skill filters out deployment-sensitive paths like src/, amplify/, and package.json to ensure only eligible files are staged.
pegasus-isiOrchestrate the software development lifecycle from testing to pull request.
har1101Commit documentation and configuration files with a [skip-cd] tag.
oborchersEnforce git tag-based production deployments with manual approval gates.
minorun365Integrate Amplify Gen2 with CDK for sandbox and production deployments.
