Analyzes project data to identify and suggest fixes for workflow inefficiencies.
npx skills add https://github.com/steve-piece/bytheslice --skill close-shop
Please help me install this Agent Skill. Skill: close-shop Source: https://github.com/steve-piece/bytheslice/tree/main/skills/close-shop Command: npx skills add https://github.com/steve-piece/bytheslice --skill close-shop
This skill addresses the lack of continuous improvement in agentic workflows by analyzing execution history to identify systemic friction patterns and drafting targeted improvements.
Invoke the close-shop skill to review the last three stages of the current project and draft a pull request for any identified workflow improvements.
High-intent search queries and answers about installing and using this skill.
Automated post-project retrospectives analyze project execution logs and git history to detect systemic friction patterns, identifying bottlenecks in skill execution and agent performance. This process generates actionable improvement proposals to refine prompts and references.
Analyzing git history for workflow bottlenecks requires reviewing stage logs and human-in-the-loop escalations to detect friction patterns. The analysis drafts targeted improvements and generates pull requests against the plugin repository to prevent recurring issues.
Yes, detecting systemic friction patterns in agentic workflows requires integration with the GitHub CLI. Accessing project-specific execution metadata and git history through the CLI is necessary to draft automated improvement pull requests for plugin maintenance.
Automated retrospectives identify systemic friction by reviewing project execution logs, git history, and human-in-the-loop escalations. This mechanism finds stages requiring multiple passes and drafts pull requests to refine prompts, skills, and references for future projects.
Yes, workflow analysis can automatically draft pull requests for plugin maintenance. By detecting friction patterns in execution logs and git history, it generates targeted code improvements to refine prompts and references directly in the repository.
You should run an automated after-service retrospective after completing a complex project or during plugin maintenance cycles. It reviews recent stage logs to debrief the shift, identify why stages required multiple passes, and propose updates to prevent future bottlenecks.
leadmind-aiExtract recurring friction patterns from logs and generate rules for CLAUDE.md.
cloudvoyantFetch open pull requests and generate proposed code fixes for unresolved review comments.
alangebPerform Git bisecting, cherry-picking, and log analysis operations locally.
auldsyababuaTriage, rebase, and verify GitHub pull requests for safe disposition.
