superdisco-moai-sync
Superdisco MoAI fork management - track customizations, sync upstream updates while preserving your changes
আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
Superdisco MoAI fork management - track customizations, sync upstream updates while preserving your changes
Create feature spec files from project docs, commit and push to main, and create matching feature branches from main.
Merge conflict resolution conventions. Use when resolving git merge conflicts, especially in dependency files and lock files.
Generates clear commit messages following project conventions
Comprehensive code review tool for Clean Code principles and project architecture. Supports single-file review (/review-code) and project-wide analysis (/review-code <directory>). Checks variable naming, function length, redundant comments, and generates actionable reports. Supports JavaScript, Python, and Java.
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", or "pr for these changes". Does NOT merge - stops when CI passes and provides the PR link.
Clone and explore external GitHub repositories to understand how libraries, frameworks, or dependencies work. Use when user provides a GitHub URL (github.com/owner/repo), asks "how does X library work", wants to look at source code for a dependency, asks about implementation details of an external package, or says "explore", "look at", or "check out" a repository. Automatically checks out the matching version tag when the repo is a dependency in the current project.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
Use when reviewing GitHub pull requests with gh CLI - creates pending reviews with code suggestions, batches comments, and chooses appropriate event types (COMMENT/APPROVE/REQUEST_CHANGES)
Fetch and analyze GitHub issues from the monorepo. Use when user asks about issues, what's blocking, issue status, dependencies, or wants to see issue details.
Identify and remove merged or stale git worktrees. Use for housekeeping, removes worktrees for branches that have been merged to main. Frees disk space.
Updates the current branch with the latest changes from origin/main using rebase. Use when the user asks to update, sync, or rebase their branch with main/master.
Analyze git diff to identify code changes requiring documentation updates. Categorizes changes (database/schema, API endpoints, components, configuration, authentication) and suggests relevant documentation files to review. Use when: (1) After making code changes, (2) Before committing significant changes, (3) When adding new features or modifying APIs, (4) During PR preparation, (5) When working with database schemas, API routes, components, or configuration files, (6) To ensure documentation stays synchronized with code changes, (7) For documentation sync and maintenance, or (8) For pre-commit documentation checks. Triggers: check docs, docs check, documentation check, update docs, sync documentation, what docs need updating, check if docs are up to date, after code changes, before committing.
Consolidate multiple PR branches onto a target branch using jj multi-parent rebase with intelligent AI-powered conflict resolution
This skill should be used when providing context about "modern CLI tools", "best practices for shell configuration", "dotfiles organization", "security patterns for configs", "performance optimization", "git configuration patterns", "modern alternatives to traditional tools", or when the main dotfiles-optimizer skill needs reference knowledge about configuration best practices.
Generate comprehensive changelogs from git history following Keep a Changelog format. Use when creating release notes or maintaining version history.
This skill should be used for detailed guidance on Jujutsu (jj) VCS operations, including committing, pushing, searching history, and working with revisions/revsets. Use it when the user asks "how do I use jj?", "translate git to jj", ask to interact with VCS using jj or for specific jj command syntax.
Create final git commit with requirement traceability tags (REQ-*). Use after refactor-phase to finalize TDD cycle with proper requirement linkage for bidirectional traceability.