Why This Matters

The CLI lessons (IN-41 to IN-45) only stick if applied. This checkpoint automates a real chore end-to-end, producing a reusable script and measuring the impact.

Concept Explained

Pick a recurring chore: lint+fix+commit, test+fix+commit, format+commit. Automate with a CLI script. Measure time saved.

How It Works

Write a shell script that runs the chore via copilot CLI: /run lint → /fix violations → /run tests → commit. Measure time saved vs manual.

Step-by-Step Tutorial

1. Pick chore

2. Write script

3. Test script

4. Measure time

5. Document

Real-World Example

A developer automated lint+fix+commit: script ran eslint, used /fix to auto-fix violations, ran tests, committed. Saved 5 minutes per PR. Across 20 PRs/week: 100 minutes saved.

Example Prompts / Commands / Code

#!/bin/bash
# lint-fix-commit.sh
set -e

echo "Running lint..."
copilot /run 'npm run lint' || true

echo "Fixing lint violations..."
copilot 'fix all eslint errors in src/, apply changes'

echo "Running tests..."
copilot /run 'npm test'

echo "Committing..."
git add .
git commit -m "chore: lint fixes (auto)"

echo "Done!"

#!/bin/bash
# test-fix-commit.sh
set -e

echo "Running tests..."
copilot /run 'npm test' || true

echo "Fixing test failures..."
copilot /fix 'npm test is failing'

echo "Re-running tests..."
npm test  # verify green

echo "Committing..."
git add .
git commit -m "test: fix failures (auto)"

Common Mistakes

• Script too complex — start simple.
• Not testing script before relying on it.
• Auto-committing without tests passing.
• Not documenting for team.

Best Practices

• Start with a simple chore (lint+fix+commit).
• Test script on a real PR before relying on it.
• Always run tests before committing.
• Document script usage in your team's wiki.
• Measure time saved; share with team.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• CLI reference

Official References

• CLI reference

Related lessons: IN-41, IN-46