work-avoidance-techniques

Automate skip decisions for PRs, builds, and configuration synchronization.

3|3|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill work-avoidance-techniques
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-avoidance-techniques
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/work-avoidance-techniques
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill work-avoidance-techniques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Layered skip checks help automate complex workflows by determining when work can be safely skipped, reducing unnecessary executions while preserving correctness.

Core Features & Use Cases

  • Layer checks for existence, content differences, and semantic changes to guide execution decisions.
  • Supports PR and build automation, configuration synchronization, and artifact management workflows.
  • Real-world scenario: automatically skip re-runs for unchanged configurations and already built artifacts.

Quick Start

Configure a multi-layer skip policy by first checking resource existence, then verify content hashes, and finally validate semantic changes to decide whether to skip or execute.

Frequently Asked Questions about work-avoidance-techniques

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I skip build automation tasks when configuration files are unchanged?

Skip checks for PR automation work by layering existence checks, content hashing, and semantic comparisons to determine whether to execute or bypass tasks, ensuring safe and deterministic outcomes for changed resources.

What is the best way to automate skip decisions for PR and build workflows?

The best way to automate skip decisions is by layering existence checks, content hashing, and semantic comparisons to evaluate resource changes, ensuring safe and deterministic outcomes for PRs, builds, and configuration synchronization.

How does content hashing work for skipping unchanged artifacts in CI pipelines?

Content hashing for skipping unchanged artifacts works by generating and comparing file hashes against previous states, allowing automation workflows to safely skip re-runs for already built artifacts and unchanged configurations.

Can I use semantic comparison to skip configuration synchronization tasks?

Yes, you can use semantic comparison to skip configuration synchronization tasks by validating semantic changes alongside existence checks and content hashing to decide whether to skip or execute safely.

When should I not use skip logic in automation workflows?

You should not use skip logic in automation workflows when deterministic execution is required regardless of file state, or when semantic comparison cannot accurately detect meaningful changes that necessitate a full task re-run.