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.
68
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Update this Mattermost plugin repository with common build/config files from the mattermost-plugin-starter-template and fix all linter issues.
git checkout master (or main)git pullgit switch -c update-from-starter-templateFetch and compare these files from mattermost/mattermost-plugin-starter-template (master branch):
Build files:
build/manifest/*.gobuild/pluginctl/*.gobuild/setup.mkMakefileConfig files:
.editorconfig.gitattributes.github/workflows/ci.yml.gitignore.golangci.yml.nvmrcgo.mod (for Go version only)server/.gitignoreWhen updating:
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.sumgithub.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.make check-style to identify issuesgo install mvdan.cc/gofumpt@latestgofumpt -w server/ to auto-fix formattingmake test to verify all tests passmake check-style to confirm 0 issuesAsk the user if they want to update all direct Go dependencies. If yes:
go get -u ./... to update all direct dependenciesgo mod tidy to clean up go.summake test to verify all tests still passmake check-style to confirm 0 issuesUpdate common files from starter template and fix linter issuesMock files have linter errors:
go generate ./...b16652d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.