antsteyer

@antsteyer source repo

16 skills
0 followers
3 hours ago last updated

▌
Pr · antsteyer
Full PR creation workflow: generate description, create GitHub PR with Jira link when branch starts with PROD-, assign it to the current GitHub user, and transition the Jira ticket to "Ready for review". Use when the user says "create a PR", "open a PR", "push and open a PR", or "/pr".

0 installs
▌
Ship · antsteyer
Run pre-flight checks (format the changed files, typecheck, specs touched by the diff), draft a commit message with the correct branch-based prefix (PROD-XXXX or #N), then commit, push, and open a PR — no approval prompts; the /ship invocation is the authorization. Use when the user says "/ship", "ship", "ship it", "shippe", "shippe ça", "commit and push", or wants to commit + push the current branch. PR creation is delegated to /pr.

0 installs
▌
Pr Flow · antsteyer bundle
Draw the mechanism of a PR as an interactive flow page — triggers, the components they reach, what fans out where — with every box opening the diff hunks and out-of-diff code it stands for. Read-only, no judgement. Use when a PR is hard to hold in the head because the change is spread across callbacks, jobs, services or entry points, and a diagram would beat a reading path; complements pr-brief.

0 installs
▌
Pr Brief · antsteyer bundle
Build a comprehension brief for one or several PRs as a local HTML page — the change explained in reading order, with every relevant diff hunk and out-of-diff excerpt embedded inline. Read-only, no judgement, no comments. Use before reviewing PRs, when I need to load a PR's context without challenging it yet.

0 installs
▌
Worktree · antsteyer
Create a git worktree as a sibling of the current repo for a GitHub issue or Jira ticket. Auto-detects the arg type (numeric = GitHub issue, `PROD-XXXX` = Jira ticket), proposes a branch name, asks the base branch, copies `.env*` and `.tool-versions` files, installs dependencies (`bun install` by default; `bundle install` + `yarn install` for agorize-core), runs the pending migrations for agorize-core, and (for GitHub issues) assigns the issue to the current GitHub user. Use when the user says "create a worktree", "worktree for #N", "worktree PROD-XXXX", or "/worktree".

0 installs
▌
Implement · antsteyer
Analyse a Jira or GitHub ticket, propose an implementation plan for validation, then implement the changes and run tests. Does NOT create a worktree (use /worktree first) and does NOT push (use /ship after). Use when the user says "/implement <url>", "implémente ce ticket", or provides a Jira/GitHub link and wants the code written.

0 installs
▌
Worked On · antsteyer
Summarize what the user has worked on since a relative date ("depuis hier", "hier midi", "cette semaine", "ce mois-ci", "depuis lundi", etc.), across the current git repo and its related sibling repo/worktrees (e.g. agorize-front + agorize-core). Reports commits grouped by ticket/branch, worktree status (clean/uncommitted/unpushed), and associated PR state. Use when the user asks "sur quoi j'ai travaillé depuis X", "qu'est-ce que j'ai fait cette semaine", "résume mon activité depuis hier", or similar.

0 installs
▌
Compile Assets · antsteyer
Recompile the agorize-core assets for production (Sprockets + Webpacker). Use when the user asks to compile, precompile, or rebuild assets in agorize-core.

0 installs
▌
Pr Description · antsteyer
Generate a pull request description by analyzing commit changes on the current branch. Use when the user asks to fill, write, generate, or create a PR description, or when opening a pull request.

0 installs
▌
Walk Pr Feedback · antsteyer
Interactive, point-by-point handling of the unresolved feedback on the current branch's PR. Builds a numbered inventory first — merged with the persisted state of any earlier pass on the same PR — then walks one point at a time: reads the code, forms a verdict, and either applies the fix and asks the user to validate before committing, asks the user to choose when several solutions or a judgment call are on the table, parks the point when it waits on a third party, or drafts a reply to the reviewer and asks for validation before sending it. Asks before pushing once at the end, then posts the approved replies in-thread, resolves the threads it addressed, re-requests the review on GitHub, and moves the Jira ticket to "Final Review" when the review it handled was AI-authored. Use when the user says "traite les retours de la PR", "on reprend les commentaires un par un", "handle PR feedback", or "/walk-pr-feedback [PR#] [start-index]".

0 installs
▌
Resolve Conflicts · antsteyer
Resolve the merge conflicts of an open PR (or rebase a branch onto its updated base) by replaying it onto the PR's REAL base branch, detecting squash-merged or stacked ancestors first, resolving conflicts file by file, running the checks the conflicted files call for, then asking before the `--force-with-lease` push. Works in agorize-front and agorize-core. Use when the user says "/resolve-conflicts [PR#]", "résous les conflits", "la PR a des conflits", "rebase sur la base", "rebase ma branche", or "fix the PR conflicts".

0 installs
▌
Sync Translations · antsteyer
Synchronize agorize-core translations (pull from Phrase, then upload to S3). Use when the user asks to sync, synchronize, pull, or update translations, including "synchroniser les trad", "sync les trads", or "/sync-translations".

0 installs
▌
Pr Review Pipeline · antsteyer
Chain the three PR passes on the PRs awaiting my review, in one go: build the comprehension brief (pr-brief), draw the flow when the mechanism is spread out (pr-flow), then leave a pending review (review-requested-prs) that reads both as context. Use when the user says "/pr-review-pipeline", "brief, flow et review", "prépare et review les PRs", or wants the three passes chained on one or several PRs. Pick this over review-requested-prs whenever the brief (and flow) must be built before the review; review-requested-prs alone is the review pass without that preparation.

0 installs
▌
Analyze Pr Feedback · antsteyer
Read-only analysis of the unresolved feedback on the current branch's PR: fetch unresolved review threads, review bodies, and general PR comments, read the code each one touches, and give Claude's point-by-point verdict (agree / disagree / to discuss) with reasoning citing path:line and a suggested action. Never edits code, commits, posts, or resolves threads — analysis only. Use when the user says "analyse les retours de la PR", "qu'est-ce que tu penses des commentaires de review", "analyze PR feedback", or "/analyze-pr-feedback [PR#]".

0 installs
▌
Review Requested Prs · antsteyer
Review the open PRs awaiting my requested review and leave pending (un-submitted) feedback I finish on the UI. Use when the user wants to go through the PRs they've been requested to review and drop pending review comments, across one or several repos.

0 installs
▌
Jira Sprint Front Tickets · antsteyer
List all FRONT tickets for a given sprint in the Agorize PROD Jira project (agorize.atlassian.net) with content summaries and story point estimates. Use this skill when the user asks to list, show, summarize, or review front-end/FRONT tickets for a sprint, mentions a sprint number (e.g. "W17", "W18", "sprint W20"), or asks "quels tickets FRONT arrivent en W17", "résume-moi le sprint FRONT", "c'est quoi les tickets front du sprint". Always invoke this skill when a Jira sprint review for FRONT tickets is requested, even if the user just says the week number.

0 installs

16 published skills