Loading...
Loading...
Found 86 Skills
Branch and PR workflow for Engram contributors. Trigger: When starting any change that will be proposed through GitHub.
Clean up local branches after PR merges. Syncs main with origin, identifies branches with merged PRs, and proposes safe deletion. Use when the user asks to 'clean up branches', 'delete merged branches', 'sync branches', or mentions branch cleanup.
Use when finishing a ticket or pull request and the user asks to validate, demo, or sign off on delivered behavior, including non-user-facing changes. Triggers include "UAT", "verify", "walk me through", "show what changed", "can we merge?", "sign off", "acceptance test", "demo this", "ready to merge", "validate the changes", "show me it works", and similar phrases indicating a need for an acceptance walkthrough or demonstration before merge.
Autonomous development agent that picks tasks from a project board (Jira, ClickUp, GitHub Issues), explores the codebase, implements the solution, opens a PR, and notifies the team. Configurable per-project via project files in ~/.config/delivering-tickets/projects/. Use this skill when the user asks to "work on a ticket", "pick up a task", "implement issue X", "work autonomously on the board", "take the next task", or any variation of autonomous task execution from a project board. Also triggers when the user mentions delivering-tickets, project configuration, or wants to set up autonomous development workflows for their team. Available commands: /delivering-tickets (start), /delivering-tickets:check (check replies), /delivering-tickets:status (workflow status), /delivering-tickets:setup (verify environment), /delivering-tickets:project (manage projects). Do NOT use for general coding without a ticket, standalone code reviews, project setup without a board configured, or questions unrelated to task execution from a project board.
Create engaging changelogs for recent merges to main branch
Hand off a task to GitHub Copilot.
Bulk resolve unresolved PR review threads. Useful after manually addressing threads or after using /pr-threads-address.
Fast-track an urgent fix through a streamlined pipeline. Skips Product/Feature Council, applies the fix, runs a focused review, and creates a PR with optional Deployment Council. Use for production bugs, security patches, or critical regressions that cannot wait for the full planning pipeline.
Pull all file comments from the current GitHub pull request and address them by making code changes.
Merge validated feature to main via PR, tag release, cleanup worktree. Use after /feature-validate passes. Use for "release feature", "merge feature", "ship it", or "/feature-release". Do NOT use without passing validation or for hotfixes that skip the pipeline.
Create or update a GitHub pull request with a Japanese title and body, using .github/pull_request_template.md or docs/pull_request_template.md when present. Use when the user asks to open a PR, create a pull request, or refresh PR metadata. Requires a pushed branch—use push (and pull if needed) first; use commit-jp for commits.
Update the pull request body for the current branch in the current repository.