aide-analyze

Topics in the source

• Smart detection
• A project with a board
• Workflow
• Step 1 of 11: Read the description
• Step 2 of 11: Analyze the codebase
• Step 3 of 11: Grade the complexity
• Step 4 of 11: Check for work already begun
• Step 5 of 11: Update 2-analysis.md

Analyze the codebase for a spec. Input: $ARGUMENTS (all arguments after the command) Parse $ARGUMENTS: The spec: the first word is its number, its folder name, or an issue key its title began with Example: /aide-analyze 55 or /aide-analyze 55-dark-mode Error handling: If the argument is missing or has an invalid format, show: -- Working interactively, hand the step to the board first: Exit 3, or no such command: go on with Step 1. Any other exit: its output is your last words; do nothing else. -- The steps below are this skill's own, inside the queue's analyze step. Mark each one in the log, so a reader can follow the run: when it starts, write one line --- Step N of X: — started, and when it ends, one line --- Step N of X: — done. A step that ends the run early says — stopped: in place of — done, and one that does not apply to this run — skipped: . Step 11, the merge into the default branch, is Aide's, after this session: Aide writes its marks, and the analyze is finished only when it is done. First write --- Step 1 of 11: Read the description — started, and when this step ends, --- Step 1 of 11: Read the description — done. Working interactively, run date +%s before anything else

This is an excerpt. Refer to the complete source and its current requirements.