engineering

Plugin engineering from marketplace gener8v-engineering in gener8v/gener8v.claude-skills.engineering. Commands read from the repo's manifest — 20 days ago.

Skills (11)

• development-commands

  Find and run a project's test, lint, type-check, build and dev-server commands, read the results correctly, and seed a throwaway database when UI work needs realistic data. Never seeds the project's real or default database. Use before 'run the tests', 'lint this', 'does it build', 'start the app so

• documentation-bootstrap

  Create or top up a project's documentation set: list what exists, let the user choose which document types to add, collect one shared fact sheet from the code, write the documents (in parallel when there are several), then check them against each other and against the code. Use when asked to 'bootst

• documentation-sync

  Before a commit, find every document that describes what the change touched and update it in the same commit, or confirm in one line that no document needs a change. Catches stale text, missing documentation and facts kept in two places. Use before any commit or PR, and when asked 'are the docs up t

• git-branching

  Put work on the correct branch before the first edit. Finds the base branch, starts a well-named branch from the current remote tip, and sets up one worktree per agent for parallel work. Use at the start of any change to a tracked file, such as 'start on issue 42', 'fix this typo', 'set up branches

• git-safety

  Approval gate for git commands that destroy work or skip checks: force-push, --no-verify, signing bypass, reset --hard, clean -f, discarding uncommitted edits, branch or tag deletion, rewriting pushed commits and push --mirror. Each one needs the user's explicit approval at that moment; an earlier a

• github-issue-filing

  Turn findings into GitHub issues: decide what is worth filing, search for duplicates, merge reports that share one root cause, split reports that need more than one fix, write each body with a clear definition of done, apply existing labels, and create the issues after the user confirms the batch. U

• github-issue-workflow

  Work one tracked item from start to close-out: confirm it is the right item and that nothing blocks it, read its requirements, plan, keep a task list, build on its own branch, prove each acceptance criterion, and hand off a PR. Works for GitHub issues and for gener8v pipeline ticket files (TICKET-NN

• github-pr-merge

  Open a pull request for finished branch work, watch its checks and reviews, and clean up branches after the merge. It never merges into the default branch on its own: merging is the user's decision unless the repository's own instructions say otherwise. Use when work is ready for review, such as 'op

• github-release

  Cut a versioned release after the work for it has merged: choose the SemVer number, update the CHANGELOG and version files through a PR, verify the build on the merged commit, then push an annotated tag and create the GitHub Release, plus a package or image if the repository publishes one. Use when

• retrospective

  Look back at a finished piece of work: what went well, what went wrong and why, and which changes to skills, project instructions, documents or tools would prevent the problems next time. Then make the changes that the user picks, through the normal branch and PR flow. 'No change needed' is a valid

• spec-writing

  Write a lightweight SPEC.md for a small project or a single feature, and turn its task list into GitHub issues with their dependencies. The GitHub-issues-native path for small work. Use when asked to 'spec this out', 'write a SPEC.md', 'turn this brief into issues', or 'what is the build order for t

Similar plugins