All authors
Claude Skills by enebin
github.com/enebin22 skills0 installs26 views
- Setup Vscode SwiftInspect and configure VS Code for Swift and Xcode development on macOS. Use when installing SweetPad and the official Swift extension, configuring Cmd+R/Cmd+B shortcuts, installing xcode-build-server, creating buildServer.json, or diagnosing SourceKit-LSP completion. Trigger for requests such as "set up VS Code for iOS development," "configure SweetPad," "fix Swift autocomplete," or "create buildServer.json."Votes: 0GitHub stars: 2
- AutolandWaits for a PR's CI checks, merges it once every check passes, then cleans up like landing. Runs takeoff first when no PR exists yet. Use for "autoland", or after takeoff when `workflow.autoland` is true.Votes: 0GitHub stars: 2
- Commit PushQuick-workflow push. Commits the current branch's changes and pushes them as they are, with no rebase and no PR, without asking for confirmation except in the warning cases. Use when the user asks to "commit and push", or after review-and-fix in the quick workflow. Step workflows ship with takeoff instead.Votes: 0GitHub stars: 2
- LandingCleans up after a PR merges. Confirms the merge, removes the issue's worktree if it has one, deletes the local branch, and updates the local integration branch. Use for "land <id>" after a PR merges.Votes: 0GitHub stars: 2
- OnboardingSets up groundwork for the current repository. Walks the user through language, issue tracker, workflow, deployment strategy, architecture, review, and screen checks (UX and QA) as pre-packaged bundles with a recommended choice each time, then writes GROUNDWORK.md and the chosen rules into the repository docs. Use when starting a new project, adopting groundwork in an existing repository, or changing earlier choices.Votes: 0GitHub stars: 2
- PlanSplits a job that does not fit in one PR into steps, and after approval creates a parent issue plus one sub-issue per step in the repository's tracker. Use for "plan this job", "split this into issues", or when another skill hands off a large job.Votes: 0GitHub stars: 2
- RejoinRemoves an issue's worktree but keeps its branch, rebased on the integration branch, as a local branch in the main checkout. Use to continue work or switch context in the main checkout, whether or not the PR has merged.Votes: 0GitHub stars: 2
- ReleaseCuts a release/<version> branch from the integration branch and opens a release PR into the production branch, with release notes and pre-release checks. Use for "release <version>" when `branches.strategy` is develop-release.Votes: 0GitHub stars: 2
- Review And FixReviews the current branch's local changes with the repository's reviewers, fixes the confirmed findings at or above a severity threshold, verifies, then commits and pushes. Use for "review and fix", or as the first half of the quick workflow.Votes: 0GitHub stars: 2
- ReviewReviews a change with the reviewers listed in GROUNDWORK.md, in parallel. Merges code findings, verifies them with Skeptic Review, and reports rendered UX and UI QA results separately. Reports only; does not modify code.Votes: 0GitHub stars: 2
- StepRuns one step sub-issue, or a standalone issue, to completion. Implements it, then repeats verify → review → fix until the review leaves no confirmed 🔴/🟠, logging each round on the issue. Use for "run step <id>", "continue <id>", a change request that has no issue yet ("fix X", "add Y"), which it files as a standalone issue first, or when another skill hands over an implemented step.Votes: 0GitHub stars: 2
- TakeoffStep-workflow push. Rebases an issue's branch on the integration branch, re-verifies, pushes it, and opens a PR, once the user asks for a push. Use for "takeoff <id>", "push and open a PR for <id>", or after a step is done.Votes: 0GitHub stars: 2
- Ui QaChecks uncovered rendered UI with an independent agent. Runs when the QA screen check triggers or on request. Scope follows the overall effort mode or explicit screens/full selection; time and token usage depend on tools and coverage.Votes: 0GitHub stars: 2
- Ux ReviewReviews whether end-user personas can finish their tasks, from the code or on the running app as ux.method says. Runs under the UX screen check or on request. Overall effort controls scope; reports only.Votes: 0GitHub stars: 2
- AddonsShow Groundwork's optional productivity skills and continue with the user's chosen setup or one-off task. Use after onboarding or when the user asks about add-ons, Slack reporting, handoff notes, weekly summaries, journey usability tests, or release preparation options.Votes: 0GitHub stars: 2
- HandoffSave or read a repository handoff note with completed work, remaining work, verification evidence, and the next starting point. Use to end a work session, hand work to another person, or resume in a new session. Does not create a new chat or send messages.Votes: 0GitHub stars: 2
- Release NotesDraft user-facing release notes for an explicit Git revision range, with features, fixes, and compatibility changes. Use to explain a release without creating release branches, tags, pull requests, or deployments.Votes: 0GitHub stars: 2
- Release PrepConfigure or run scheduled release preparation, infer a version from the release diff, verify the candidate, and present release notes and a reasoned version recommendation for final yes-or-no publication approval. Use for recurring release preparation or preparing the next release for approval.Votes: 0GitHub stars: 2
- Slack ReportConfigure or post repository work reports to the user's chosen Slack workspace, with one thread per work branch. Use when asked to report to Slack, configure Slack reporting, or when an opted-in turn-end hook requests a report. Do not post merely because onboarding lists this add-on.Votes: 0GitHub stars: 2
- UpdateBrings a repository already set up with groundwork up to the installed plugin version. Reads the plugin's change list between the version the repository was set up with and the installed one, applies required migrations, lets the user pick which new features to attach, and refreshes rule blocks whose text changed. Does not repeat onboarding, except that it points to onboarding when an update brings more than 8 choices. Use after updating the plugin, or for "what's new in groundwork", "update ...Votes: 0GitHub stars: 2
- Ux JourneyRuns a usability test of an end-to-end user journey, such as landing page → sign-up → organization setup, on the running app. A participant agent that has not seen the code walks each journey from a clean state while this skill moderates and reports where users hesitate, get lost, or give up. On first run it explores the project, proposes journeys, and asks the user to confirm them. Use on request, after changing first-run screens, or as a release gate when ux.journey is release.Votes: 0GitHub stars: 2
- Weekly SummaryDraft an evidence-based weekly repository summary from commits, pull requests, and issues. Use for a weekly update or retrospective. Runs on demand; does not schedule recurring work or post to another service unless explicitly requested.Votes: 0GitHub stars: 2