Loading...
Loading...
Found 8,855 Skills
Use after the final approved execution scope is complete, or when the user asks whether a feature is done, ready to ship, safe to merge, or needs a quality check. Runs the post-execution quality gate: specialist review, artifact verification, and human UAT against locked decisions and the final exit state. Use for prompts like "review this feature", "is this done?", "can we ship this?", "double-check the implementation", or "run UAT".
Lance une réunion autonome rapide avec des personas sélectionnés automatiquement, implémente la décision, crée une MR/PR, commite, pousse et publie un résumé en français — le tout sans intervention de l'utilisateur.
Post-session retrospective: audits efficiency, proposes skill/memory/CLAUDE.md updates, and generates coaching feedback
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Full autonomous execution from idea to working code
Design research plans and paper architectures. Given a research topic or idea, generate structured plans with methodology outlines, paper structure, dependency-ordered task lists, UML diagrams, and experiment designs. Use when starting a new research project or paper.
Split uncommitted changes into focused, logical commits using git-hunk. Use when asked to "split changes", "split commits", "organize commits", "commit by hunk", or "separate changes into commits".
Review code changes against STYLE_GUIDE.md before committing or creating PRs. Catches naming violations, import ordering issues, anti-pattern reintroduction, and convention drift. Run after /setup-ai or /generate-comprehensive-style-guide has created a style guide.
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
Review the latest changes and check whether they comply with the project's documented guidelines (AGENTS.md, CLAUDE.md, or equivalent). Use when reviewing local diffs, recent commits, or feature work and you need a findings-first assessment of architecture, reuse, testing, and repo-specific rules.
Use when working with the `arise` CLI to check readiness, generate review-first plans from strict PRDs or GitHub issues, inspect `.arise/` artifacts, execute reviewed plans, or recover interrupted and integration-blocked runs.