Loading...
Loading...
Found 21 Skills
Collaborative problem-solving protocols: write technical specifications (spec, or alspec), create implementation plans (plan, or alplan), or use Align-and-Do Protocol (AAD). Also generates PR/MR descriptions (aldescription).
Generate comprehensive PR descriptions following repository templates
Write a description to description GitHub Pull Request.
Automate PR workflows. Use before creating PRs. Generates PR descriptions, validates PR requirements, checks for missing tests/docs, and links issues automatically.
Checks a GitHub pull request for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR, address review feedback, or prepare a PR for merge.
Detect AI-generated writing patterns in developer text — docs, docstrings, commit messages, PR descriptions, and code comments. Use when reviewing any text artifact for authenticity and clarity.
Delivery Report Skill for Team Workflows (Phase 4). Generate PR Description (referencing plans/designs/verification items) and optionally sync with Jira Story.
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
Write a description summarizing implemented work. Generates PR/MR descriptions from completed changes.