Explorar skills

Use when starting feature work that needs workspace isolation — creates git worktree with automatic project setup and baseline test verification. Ensures worktree directory is git-ignored and safe. Integrates with code-forge:impl and code-forge:finish.

Generates a CI/CD pipeline configuration for the project. Auto-detects the stack and creates GitHub Actions, GitLab CI, or other CI configs with lint, test, build, and deploy stages.

Use when commits on a feature branch are messy, out of logical order, mix unrelated changes, or need restructuring before a PR - also triggered by "clean up history", "reorganize commits", "recompose branch", "make commits logical", or similar

Detect, classify (porcelain status; complexity: trivial, semantic, structural, delete-modify), and resolve git merge conflicts through per-file strategy selection (accept-ours, accept-theirs, manual-merge, rebase), manual conflict hunk parsing, and post-resolution verification (orphaned markers, build, tests). Use when a branch has conflicts with its merge target or when rebasing onto an updated b

{{ ƔƔƔ }} Rename branch if needed

Display code-forge feature dashboard with task-level progress from state.json, or show detailed status for a specific feature. Use when checking progress, asking "what's left", viewing task completion, or wanting a bird's-eye view of the project.

Generates a changelog from git history following Keep a Changelog format. Categorizes commits into Added, Changed, Fixed, Removed, Security, and Breaking Changes. Use before releases or to document recent work.

Cleans up stale git branches, merged branches, orphaned remote refs, and identifies large files in history. Use for periodic repository maintenance.

Esta skill constrói seu backlog editorial a partir da demanda real e verificável do usuário, nunca de "vibes" de IA. Ela extrai tópicos de diversas fontes como Google Suggest, Reddit e Stack Overflow, classificando-os por formato de post.

Automate Lemon Squeezy tasks via Rube MCP (Composio): products, orders, subscriptions, checkouts, and digital sales. Always search tools first for current schemas.

Bug → spec protocol. On bug found ∨ test fail → trace cause, decide if new §V invariant catches recurrence, append to §B. Triggers: test failure, bug report, post-mortem, explicit user ask. Phrasings: "X broke", "we got bit by", "post-mortem on Y", "this should never recur", "add a §V for". ⊥ for mechanical typo ∨ one-off fix w/ ⊥ recurrence class — pure code fix only.

Uma skill que prioriza regras para gerar, migrar e validar artefatos de aplicativos 1Panel em ambientes Linux e fluxos de trabalho do GitHub.