Loading...
Loading...
Found 55 Skills
Create or update living documentation from git history (branch diff, current branch, PR, or last N commits) for microservices. Use when users ask to document a feature/funcionalidad, document current branch/branch actual, generate release notes/changelog, explain what changed, or update docs for react, integrator, magento, or all services. Produces docs in each repo's docs/ folder (components, changelogs, adrs, runbooks, guides, technical, bugs, plans, tasks) with traceability to commits/files and Obsidian-compatible frontmatter.
Backend-agnostic task management. Use when: (1) creating, listing, updating, or archiving tasks; (2) analysing task status; (3) setting up task backend. NOT for: memory population (use memory); session management (use memory session).
Session retrospective and codification. Run at the end of any significant session to extract learnings, update documentation, and create artifacts that make future sessions smoother. Invoke when: - Finishing a multi-step implementation - After debugging a hard problem - End of any session with 3+ tool calls - "what did we learn?" / "wrap up" / "done" Subsumes /codify-learning (codification is one output, not the only one).
Daily startup and closeout rituals. Use when: (1) starting the workday; (2) wrapping up the day. NOT for: mid-day task management (use task); compound loop (use work); memory directly (use memory).
Compound engineering loop — 5 stages to reduce rework. Use when: (1) starting new work (brainstorm); (2) planning implementation (plan); (3) writing code (work); (4) evaluating output (review); (5) capturing lessons (compound). NOT for: daily rhythm (use daily); task management only (use task).
Run all groove health checks: config, backends, companions, AGENTS.md.
Write the daily memory log entry. Use at end of day to record what happened.
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any provider (Codex, Gemini, GPT, Claude, etc.). Use after creating a handoff or when ready to get an AI code review.
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
Set up and run an autonomous experiment loop for any optimization target. Gathers what to optimize, then starts the loop immediately. Use when asked to "run autoresearch", "optimize X in a loop", "set up autoresearch for X", or "start experiments".
Detect exposed secrets, API keys, credentials, and tokens in code. Use before commits, on file saves, or when security is mentioned. Prevents accidental secret exposure. Triggers on file changes, git commits, security checks, .env file modifications.
Use beads (bd) for persistent task tracking in coding projects. A git-backed issue tracker designed for AI agents with dependency graphs, hierarchical tasks, and multi-agent coordination.