testing-cli

name	testing-cli
description	Tests the yeet-git CLI tool by performing file edits and running various git command scenarios to verify functionality. Use when the user asks to test the CLI commands.

Testing Yeet Git CLI

When to use this skill

• When the user asks to "test the CLI" or "verify commands".
• When you need to ensure the yeet tool is working correctly after changes.
• To validate specific git workflows supported by the tool.

Workflow

1. Setup Work Area: Create or verify existence of a simple text file (e.g., test_playground.txt) in the root directory.
2. Iterative Testing: For each test case:
   • Modify the test_playground.txt file (append a timestamp or random string) to ensure git detects a change.
   • Run the specific yeet command.
   • Verify the output and git status.
3. Cleanup: Optionally revert changes to test_playground.txt or leave it for history.

Test Commands Checklist

Copy this checklist to task.md or use it to track your progress.

Basic Operations

• yeet --c
  • Goal: Commit current changes with AI-generated message.
  • Expectation: git add . runs, AI generates message, commit is created.
• yeet -cp
  • Goal: Commit and Push.
  • Expectation: Same as above, plus git push.

Merge Flows (Dev)

• yeet --to-dev --merge
  • Goal: Merge current branch into dev.
  • Expectation: Switch to dev, merge original branch.

Multi-Stage Flows (Staging)

• yeet --to-dev-staging --label
  • Goal: Merge to dev, then PR to staging with static label.
  • Expectation: Current -> Dev (Merge) -> Staging (PR/NoMerge + Label).
• yeet --to-dev-staging --merge
  • Goal: Merge to dev, then merge to staging.
  • Expectation: Current -> Dev (Merge) -> Staging (Merge).
• yeet --to-dev-staging --merge --label-[MyLabel]
  • Goal: Merge to dev, merge to staging with custom label.
  • Expectation: Current -> Dev (Merge) -> Staging (Merge + Label=MyLabel).

Full Pipeline (Main)

• yeet --to-dev-staging-main --merge
  • Goal: Propagation to Dev, Staging, and Main.
  • Expectation: Current -> Dev (Merge) -> Staging (Merge) -> Main (Merge).

Instructions

• Safe Execution: Always check git status before running these commands to know where you are.
• Modifications: The test_playground.txt file is your sandbox. Don't modify critical project files for these tests.
• Extending Tests: Add new command variations to this list as the project evolves and new flags are implemented.
• Command Alias: If yeet is not in the global path, use node ./bin/yeet.js or the appropriate relative path to the binary.