gslava
- 14 skills
- 0 followers
- 6 hours ago last updated
- ▌ Execute Implementation Plan · gslava bundleSafely execute an existing implementation plan task by task. Use when the user asks to implement, execute, run, continue, or finish a plan file or checklist, especially plans under docs/plans or Codex-created implementation plans.
- ▌ Cut Release · gslava bundlePrepare and optionally publish a software release with explicit safety gates. Use when the user asks to create, cut, prepare, publish, tag, or bump a release/version; generate release notes; update a changelog for release; or publish a release after explicit confirmation.
- ▌ Reset Approach · gslava bundleRecover after an attempted solution path has failed, become over-complicated, repeatedly failed verification, or the user rejects the current implementation direction. Use to pause, preserve useful work, reframe the problem, and choose a better path before more edits; not for ordinary git reset, undo, or revert requests.
- ▌ Brainstorm Design · gslava bundleCollaborative design workflow for significant software changes: new features, architecture decisions, refactors, migrations, and ambiguous code implementation requests. Use before writing code when the right technical solution is unclear, risk is non-trivial, or multiple codebase-compatible approaches exist.
- ▌ Clarify Confusion · gslava bundleResolve user confusion, expectation mismatches, contradictory assumptions, and surprising behavior questions before deciding whether to explain, document, configure, fix, or plan. Use investigate-root-cause instead for failing commands, logs, stack traces, or concrete failures.
- ▌ Dialectic Analysis · gslava bundleStress-test claims, architecture decisions, refactors, performance assumptions, safety claims, and proposed solutions by arguing both for and against them. Use when the user asks to prove/disprove, challenge, sanity-check, stress test, argue both sides, or decide whether a claim is really true.
- ▌ Review Pull Request · gslava bundleReview GitHub PRs, merge requests, or local branch diffs with code evidence. Use when the user asks to review PR/MR changes, check a branch diff, produce review findings, or draft a PR review comment; use issue-specific workflows for issue triage without a PR diff.
- ▌ Clarifying Questions · gslava bundleCheck whether a request is clear enough before planning, editing, executing, publishing, or giving a final recommendation. Use when missing details could change scope, target behavior, permissions, acceptance criteria, or other decision-critical outcomes.
- ▌ Investigate Root Cause · gslava bundleSystematic debugging and root cause analysis for concrete failures: errors, failing tests, build failures, logs, stack traces, flaky behavior, performance regressions, integration failures, and reproducible wrong behavior. Use before applying fixes when the cause is uncertain; use clarify-confusion for expectation mismatches without failure evidence.
- ▌ Technical Writing Style · gslava bundleApply concise, direct engineering communication for engineering artifacts: PR comments, issue comments, code review feedback, commit messages, implementation summaries, status updates, and technical decisions. Use when the user asks to rewrite, shorten, make direct, or remove AI-sounding language from technical engineering text.
- ▌ Make Implementation Plan · gslava bundleCreate rigorous implementation plans for feature work, bug fixes, refactors, migrations, test work, and multi-step code changes. Use when the user asks for a plan, roadmap, implementation plan, task breakdown, or when a change is large enough that coding immediately would hide risk.
- ▌ Capture Project Knowledge · gslava bundleCapture reusable project instructions discovered during a session, such as architecture, conventions, testing patterns, build commands, operational notes, gotchas, and integration details. Use when the user asks to save durable project knowledge, update AGENTS.md, update project instructions, or preserve lessons that should affect future Codex sessions.
- ▌ Inspect Unreleased Changes · gslava bundleSummarize unreleased git, commit, PR, or release changes since the last tag, release, or user-specified base. Use for commits since last tag, unreleased changes, changelog prep, release notes prep, or release impact review; do not use for broad product 'what is new' questions unrelated to repository history.
- ▌ Review Implementation Plan · gslava bundleReview implementation plans before coding. Use when the user asks to review, validate, sanity-check, de-risk, simplify, or find gaps in a plan, especially docs/plans files, task checklists, migrations, refactors, and multi-step feature plans.