docs

Plugin docs from marketplace zadykian in zadykian/skills. Commands read from the repo's manifest — 18 days ago.

Skills (7)

• atomic-commits

  Use when implementing code changes in a git repo - deliver small, self-contained Conventional Commits, and split any change over 300 diff lines into a stack of independently mergeable PRs.

• banned-terms

  Keep vague names and fillers, such as helper, utils, misc and simply, out of new code and prose. Use when naming a file, type, function or variable, and when writing a comment, a doc, a commit message, or a pull request's title and body. - "**/*.md" - "**/*.go" - "**/*.py" - "**/*.sh" - "**/*.js" -

• issue

  Plan a change, then file it as a GitHub issue in a compact house style once the maintainer approves the plan. Use when asked to file, open or write up an issue, or to plan a change as one.

• land

  Land a stack of approved pull requests on main, bottom first, by fast-forward through a /ff comment, and tag a release if asked.

• split-file

  Split a source file over the repository's line cap into files by responsibility, in its package or module and with its API unchanged. Use when a size check reports a file over its cap.

• trim

  Trim a repository's code comments or Markdown docs to the writing policy and its Vale rules, keeping every fact. Use on files that fail Vale or the comment caps, or that restate the code or the help.

• writing

  The writing policy for code comments and docs: a comment gives a purpose or a reason, each fact lives in one place, and short sentences pass Vale's rules. Use when writing or editing comments, Markdown or other prose in a repository. - "**/*.md" - "**/*.go" - "**/*.py" - "**/*.sh" - "**/*.js" - "**/

Similar plugins