Autonomous Decision Making
Medium
- Category
- Excessive Agency
- Confidence
- 75% confidence
- Finding
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Content
md l_request` first and read its `commits` plus `exactDiff`. Use the connected read bridge afterward when private access, branch history, check runs, reviews, or additional commit metadata is needed. - **Changelog in a date range:** combine releases/tags with commits or merged pull requests in the same range. Prefer release notes when present, group changes by feature/fix/maintenance only when evidence supports it, and link or identify the underlying releases, PRs, or commits returned by GitHub. When a repository name is unique in the connected account, select it without asking for a redundant `owner/repo`. If multiple repositories match, show the short candidate list and ask which one. Reads may run directly. Before creating or changing issues, pull requests, releases, files, branches, comments, stars, or repository settings, show the exact GitHub account, repository, action, and submitted fields and obtain confirmation unless the current message already authorizes those exact details.
