update-from-starter-template
Update Mattermost plugin repositories with common files from mattermost-plugin-starter-template and fix all linter issues. Use when syncing build tooling, updating golangci-lint config, or fixing linter errors in a Mattermost plugin.
What this skill does
# Update from Starter Template Update this Mattermost plugin repository with common build/config files from the [mattermost-plugin-starter-template](https://github.com/mattermost/mattermost-plugin-starter-template) and fix all linter issues. ## Instructions ### Phase 0: Prepare the repository 1. Switch to the main branch: `git checkout master` (or `main`) 2. Pull latest changes: `git pull` 3. Create a new branch for the updates: `git switch -c update-from-starter-template` ### Phase 1: Update common files from starter template Fetch and compare these files from `mattermost/mattermost-plugin-starter-template` (master branch): **Build files:** - `build/manifest/*.go` - `build/pluginctl/*.go` - `build/setup.mk` - `Makefile` **Config files:** - `.editorconfig` - `.gitattributes` - `.github/workflows/ci.yml` - `.gitignore` - `.golangci.yml` - `.nvmrc` - `go.mod` (for Go version only) - `server/.gitignore` When updating: - Preserve plugin-specific customizations (plugin ID, custom targets) - Update tool versions (golangci-lint, gotestsum, Node.js) - Adopt new linter configurations - Update Go version in `go.mod` if the starter template uses a newer version (compare the `go` directive). Also update the Go version in `.github/workflows/ci.yml` to match. After updating, run `go mod tidy` to update `go.sum` - Preserve license headers - Some plugins use `github.com/mattermost/mattermost-govet` in their Makefile to check for license headers. Do NOT remove that linter. If it reports missing license headers, add them to the affected source files. ### Phase 2: Fix linter issues 1. Run `make check-style` to identify issues 2. Install gofumpt if needed: `go install mvdan.cc/gofumpt@latest` 3. Run `gofumpt -w server/` to auto-fix formatting 4. Fix remaining issues manually ### Phase 3: Verify and commit 1. Run `make test` to verify all tests pass 2. Run `make check-style` to confirm 0 issues 3. Create a descriptive commit and PR. Use the pull request template from https://github.com/mattermost/.github/blob/master/PULL_REQUEST_TEMPLATE.md. ### Phase 4: Update Go dependencies (optional) Ask the user if they want to update all direct Go dependencies. If yes: 1. Run `go get -u ./...` to update all direct dependencies 2. Run `go mod tidy` to clean up `go.sum` 3. Run `make test` to verify all tests still pass 4. Run `make check-style` to confirm 0 issues 5. Create a separate commit for the dependency updates ## Example commit message ``` Update common files from starter template and fix linter issues ``` ## Troubleshooting **Mock files have linter errors:** - Generated mocks may need regeneration: `go generate ./...` - Or exclude from linting if they're third-party generated
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.