358 skills · sorted by relevance
Launch and troubleshoot the actual AO desktop app to inspect interface changes with local data. Supports reviewing combined pull request branches and diagnosing lingering Electron processes, port conflicts, and mismatches in the app’s preload bridge.
Prepare and publish DeepChat releases through its project-specific workflow. Update versions and bilingual changelogs, run release checks, manage release branches and tags, and resume unfinished releases before publishing after release PR approval.
Create and validate mirrord.json settings for isolated database copies used in development and testing. Configure connection sources, copying scope, migrations, and authentication so experiments can run without affecting shared databases.
Organize dependent code changes into a chain of branches and pull requests, so reviewers can examine one layer at a time. The skill guides stack creation, edits, synchronization, rebasing, and merging with gh-stack.
Run Tamanu pre-release verification checks: verify that hotfixes on the current release branch are merged forward to main, and that hotfixes from prior release branches are included in the current release. Use when the user wants to run "pre-release checks", verify hotfix integrity before cutting or shipping a Tamanu release, confirm a release/X.YY branch is safe to release, or check that no hotfix has been orphaned (left on neither main nor the current release). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for deciding which tests to run (see scope-tamanu-release-tests).
The English summary is being prepared. Showing the original description.
Reißverschluss-Verfahren (englisch: zipper merge) für sehr konfliktreiche Merges: Wenn zwei divergente Branches oder ein PR und sein Zielbranch BEIDE wertvolle, unvereinbar erscheinende Änderungen tragen, wird nicht pauschal eine Seite gewählt, sondern Abschnitt für Abschnitt verglichen, per Entscheidungstabelle (Nimm/Warum) die jeweils bessere Version übernommen, abschnittsweise committet und erst am Ende gepusht. Letzte Eskalationsstufe: Rebuild statt Merge — nur die Absicht/Funktionalität des Branches übernehmen und auf dem aktuellen Stand neu bauen. Nutzen bei: "Merge-Konflikt", "divergente Branches", "main vs. master", "konfliktreicher PR", "zipper merge", "Reißverschluss", "beide Seiten haben Recht", "PR ist zu alt zum Mergen".
The English summary is being prepared. Showing the original description.
Safely clean up local branches whose tracked remote branch is gone. Use when you want to review stale branches and associated worktrees after remote branches or PRs are deleted.
The English summary is being prepared. Showing the original description.
Clean up git branches marked as [gone] (deleted on remote but still exist locally). Use when you want to prune stale local branches, remove worktrees for deleted branches, or clean up after PR merges.
The English summary is being prepared. Showing the original description.
Break an RFC, a written design proposal, into work units with dependencies and acceptance tests for multiple agents. Organize research, implementation, testing, review, queued merges, and final system verification for features too large for one pass.
Organize code changes into focused commits and manageable branches, prepare pull requests, and maintain release versions and changelogs. The skill also covers separate working directories for parallel work and checks before committing.
Tidy a Paperclip Mine inbox by scanning entries and grouping archive candidates by work status and inactivity. Present checkbox confirmations, then archive only accepted selections, with undo details and no changes to the underlying tasks, branches, or workspaces.
Turn workflows and system flows into a whiteboard-style diagram with colored sticky notes and curved arrows. The skill produces a single HTML file, with branches, merges, and optional hover effects for onboarding or operational explanations.
Audit the macOS and Windows branches of Mole CLI for safety risks, excess complexity, outdated information, performance issues, and lessons missing from tests or rules. Challenge each finding before reporting it, then implement and record approved fixes.
Analyze compiled programs without running them by recognizing branches, loops, data structures, and common instruction patterns. Use disassembly and decompilation, which translate machine code into readable representations, to reconstruct program logic and document findings.
Organize feature development across multiple agents by dividing work, assigning one owner per file, and agreeing on interfaces before implementation. Provides strategies for shared files, branches, and integration so agents can build separate parts of the same system.
Analyze current Git changes to choose a branch for a feature, release, or urgent fix. Create a descriptive name and switch to the new branch using Git Flow, a structured approach to managing development branches.
Route Git tasks to a dedicated agent to organize commits, branches, and project history. It supports focused commits, repository commit style detection, and interactive rebasing, which lets you reorganize existing commits.
Trace how one idea developed across stored notes and records. Identify its earliest documented mention, clearest expression, changes of stance, contradictions, abandoned branches, and current form, with dated evidence and explicit gaps where sources are missing.
Navigate the Composio SDK monorepo, a repository containing multiple packages, and follow its shared development rules. Use it to decide where changes belong, handle generated files and release metadata, and prepare branches and pull requests.
Handle critical bugs in a released game through an emergency workflow. Investigate the cause, prepare a minimal fix, track reviews and tests, and verify the fix reaches development branches, with deployment approval and post-release checks recorded.
Inventory feature flags, switches that control feature availability, and remove eligible flags with their unused code branches. Leave ongoing rollouts and experiments untouched, run verification checks, and prepare a pull request for human review.
Manage Git branches, resolve conflicting changes, organize commit history, and recover earlier work after mistakes. Also helps teams choose a branching workflow that fits how they review changes, integrate work, and release software.
Remove a specific Git worktree, a separate working directory for a branch, after checking uncommitted work and merge status. Clean up branches and stale references, protect important branches, and provide reminders for related database cleanup.
Browse Git branches and historical versions to prepare a rollback. Choose reset to rewrite branch history or revert to create undo commits while preserving it, preview the planned commands, and execute after confirmation.