TheEdoRan
- 4 skills
- 0 followers
- 20 hours ago last updated
- ▌ GCP · theedoran bundleStage changed files, create logical commits, split unrelated concerns into separate commits, push the current branch, and verify the result. Use only when the user explicitly invokes /gcp or $gcp or asks to run the GCP git workflow; accept any accompanying text as optional commit-message guidance.
- ▌ Explain · theedoran bundleRead-only analysis of a feature's implementation (or the work just completed in the conversation) across security, performance, maintainability, and edge cases. Writes findings to a markdown report file for the user to act on; changes no code. Verifies security and library best practices against current documentation via Context7. Invoke only when the user explicitly requests `/explain` or `$explain`, optionally naming the feature, paths, or diff to analyze.
- ▌ Explain Fix · theedoran bundleAnalyzes the implementation of a feature (or the work just completed in the conversation) across security, performance, maintainability, and edge cases, then hardens it test-first — same analysis as the `explain` skill, but the fixes are applied instead of left to the user. Invoke only when the user explicitly requests `/explain-fix` or `$explain-fix`, optionally naming the feature, paths, or diff to analyze.
- ▌ Explain Implementation · theedoran bundleExplains a completed implementation as a decision-oriented walkthrough of what changed, how it works with file:line references, and why key choices were made. Uses session-verified documentation and a persistent knowledge memory to avoid repeating known concepts. Invoke only when the user explicitly enters `/explain-implementation` in Claude Code or `$explain-implementation` in Codex. Do not invoke for natural-language requests to explain or walk through code, unsolicited post-task summaries, general concept tutorials, changelogs, or docstrings.