BrOrlandi
- 11 skills
- 0 followers
- 1 week ago last updated
- ▌ Jira · brorlandi bundleInteract with Jira using the jira CLI and REST API. View, create, list, transition, and comment on issues. Supports proper @mentions that notify users. Query activity reports showing who did what (created, edited, commented, moved issues, etc.) over a time period. Use when the user wants to work with Jira issues — view a ticket, add a comment, mention someone, list issues, create tasks, move issues between statuses, assign issues, or check recent activity/what was done.
- ▌ Slack · brorlandiSend messages, upload files and images, read conversations, react to messages, and manage Slack workspaces using SlackCLI. Use when the user wants to interact with Slack — send a message, share a file, upload images or screenshots, read channel history, find a user, react to a message, or check workspace auth.
- ▌ Commit · brorlandi bundleCreate structured git commits from the current repository changes. Use when the user asks to commit, create a commit, prepare commits, run the old /commit workflow, or turn local staged/unstaged changes into one or more conventional commits.
- ▌ Release · brorlandi bundleEstablish and then run a repository's release convention: semantic version bump, changelog and release notes written from the commits since the last release, git tag, GitHub release with versioned assets, in-app or public changelog screens, and app store notes. The first time it runs in a repo it detects the stack (web app, Android, iOS, macOS/desktop binary, library/CLI, or a monorepo holding several apps), agrees the convention with the user, and records it in `.claude/release.json` plus a short CLAUDE.md section — so every later run, and any agent working without this skill, knows where the version lives, which changelog to update, and how the release is published. Use this skill whenever the user mentions release notes, changelog, novidades, semantic versioning, "fechar uma versão", "nova versão", "subir a versão", "bump", tags, GitHub releases, publishing a build to a store, or asks what changed since the last release. Also offer it proactively right after a PR is created or merged and after finishing a
- ▌ Pr Review · brorlandiReview a GitHub Pull Request and submit a single review with inline code comments. Identifies bugs, security vulnerabilities, performance issues, logic errors, missing edge cases, and suggests improvements. Use when the user wants to review a PR, do a code review, or add review comments to a pull request.
- ▌ Pr Comments · brorlandi bundleFetch PR review comments in sequential order, perform deep analysis with code context and impact assessment, suggest concrete solutions with alternatives, enter Plan mode for complex changes, and auto-resolve threads on GitHub.
- ▌ Refactor Code · brorlandiFind large non-React code files (.ts/.js) with too many responsibilities and refactor them into smaller, focused files. Works with API routes, services, utilities, hooks, middleware, schemas, and other TypeScript/JavaScript files. Does NOT handle React components (.tsx/.jsx with JSX) — use refactor-components for those.
- ▌ Todo Resolver · brorlandiFind TODO comments in the codebase, analyze their impact and complexity, and optionally implement the changes to resolve them. Use when the user wants to find, triage, or resolve TODO/FIXME/HACK comments.
- ▌ Pr Screenshots · brorlandi bundleCapture screenshots or GIF recordings of a new UI feature, upload them losslessly to a GitHub orphan branch (pr-assets), and add a Screenshots section to the current PR description. Supports spotlight effects that highlight specific components with a dark overlay, rounded cutout, and explanatory annotations based on the PR diff. Can temporarily modify source code to force UI states, add selectors, or simulate data for accurate captures — all changes are safely reverted after. Images are served via github.com blob URLs which work for both public and private repos. A "local" mode saves captures to the user's Downloads folder and inserts a Screenshots section with [Pending] placeholders so the user pastes the images into the PR themselves — nothing is committed or uploaded. Use when the user wants to visually document a feature in a pull request — triggered by phrases like "add screenshots to my PR", "document this feature visually", "screenshot the new screens", or "record a GIF of this flow".
- ▌ Autonomous Mode · brorlandiWork through a task from start to finish on your own judgment without interrupting the user — never use the AskUserQuestion tool while the task is running. When you hit an ambiguous decision, choose the most sensible reversible option, log it, and keep going until the objective is fully met. Collect every real question you would normally stop to ask, defer them all to the end, then tell the user the work is done and to ask for a review; surface the questions only when they request the review — and if none came up, say so. Make sure to use this skill whenever the user signals they want you to push a task to completion on your own and only check in at the end: "modo autônomo", "não me pergunte", "não me interrompa", "trabalhe até o fim", "implemente tudo sem parar", "faz tudo e me mostra no final", "work autonomously", "don't ask me questions", "stop interrupting me", "just finish it", "do the whole thing and report back" — even if they never use the word "autonomous".
- ▌ Refactor Components · brorlandiFind large React components (.tsx/.jsx) with too many responsibilities and refactor them into smaller, focused components. Use when the user wants to clean up or split large components.