All authors
Claude Skills by Pharaoh-so
github.com/Pharaoh-so20 skills0 installs0 views
- PharaohCodebase knowledge graph with 8 development workflow skills. Query architecture, dependencies, blast radius and dead code via MCP. Requires GitHub App installation (read-only repo access) and OAuth authentication. Connects to external MCP server at mcp.pharaoh.so.Votes: 0GitHub stars: 2
- BrainstormExplore intent, requirements, and design before implementation. Collaborative dialogue to turn ideas into specs. Ask clarifying questions one at a time, propose 2-3 approaches with trade-offs, get approval before writing any code. Prevents wasted work from unexamined assumptions.Votes: 0GitHub stars: 2
- DebugSystematic 4-phase debugging methodology. Root cause investigation before any fixes. Read errors carefully, reproduce consistently, trace data flow, form hypotheses, test minimally. If 3+ fixes fail, question the architecture. No guessing, no quick patches, no symptom fixes.Votes: 0GitHub stars: 2
- PharaohCodebase knowledge graph — gives AI agents full architectural awareness. Query architecture, dependencies, blast radius, module context, and function search instead of reading files one at a time. Code intelligence via MCP: understand any codebase in seconds.Votes: 0GitHub stars: 2
- PlanReview a plan or spec against the codebase before implementing it. Pharaoh reconnaissance, a BIG or SMALL change choice, then architecture, code quality, wiring, tests, performance and security sections with numbered decisions.Votes: 0GitHub stars: 2
- RefactorSafe refactoring workflow using Pharaoh codebase knowledge graph. Six-step process: module context, blast radius of detected downstream callers, reachability verification, dependency mapping, naming conflict detection, and a search for the affected tests. Produces a refactoring plan with detected callers listed, test files identified, unreachable code flagged, and high-risk paths warned. Use when refactoring, renaming, moving or splitting code in a repo Pharaoh maps, with Pharaoh's tools conn...Votes: 0GitHub stars: 2
- ReviewFive-phase workflow: git context detection (worktree, branch, base, changed files), Pharaoh recon (architecture map, module context, blast radius in one call, with a fallback when the repo isn't mapped), parallel specialized agent dispatch (code quality, security against the project's own rules, error handling, test coverage, type design), adversarial review by the other model (Codex from Claude Code, Claude from Codex) for security-sensitive changes, and a final synthesized verdict of SHIP /...Votes: 0GitHub stars: 2
- TddTest-driven development discipline. Write the failing test first, watch it fail, write minimal code to pass, refactor. No production code without a failing test. No exceptions without explicit permission. Covers red-green-refactor cycle, common rationalizations, and when to start over.Votes: 0GitHub stars: 2
- VerifyEvidence before assertions. Run verification commands and confirm output before claiming work is complete, fixed, or passing. No 'should work now' — run the command, read the output, then claim the result. Covers tests, builds, linting, agent delegation, and requirement checklists.Votes: 0GitHub stars: 2
- PharaohWhich Pharaoh tool answers which structural question about a mapped repo (TypeScript, JavaScript, Python): where code lives, what calls it, what a change affects, what a module contains and what nothing runs. Use when Pharaoh's tools are connected and the question is about the structure of a repo Pharaoh maps.Votes: 0GitHub stars: 2
- PlanReview a plan or spec against the codebase before implementing it. Pharaoh reconnaissance, a BIG or SMALL change choice, then architecture, code quality, wiring, tests, performance and security sections with numbered decisions.Votes: 0GitHub stars: 2
- RefactorSafe refactoring workflow using Pharaoh codebase knowledge graph. Six-step process: module context, blast radius of detected downstream callers, reachability verification, dependency mapping, naming conflict detection, and a search for the affected tests. Produces a refactoring plan with detected callers listed, test files identified, unreachable code flagged, and high-risk paths warned. Use when refactoring, renaming, moving or splitting code in a repo Pharaoh maps, with Pharaoh's tools conn...Votes: 0GitHub stars: 2
- ReviewFive-phase code review: git context (branch, base, changed files), Pharaoh recon (architecture map, module context and blast radius, with a fallback when the repo isn't mapped), parallel specialized reviewers (correctness, security against the project's own rules, error handling, tests, types), an independent second-opinion pass for security-sensitive changes, and a SHIP / SHIP WITH CHANGES / BLOCK verdict. Architecture-aware wherever Pharaoh maps the repo. Use when reviewing a branch or pull...Votes: 0GitHub stars: 2
- BrainstormExplore intent, requirements, and design before implementation. Collaborative dialogue to turn ideas into specs. Ask clarifying questions one at a time, propose 2-3 approaches with trade-offs, get approval before writing any code. Prevents wasted work from unexamined assumptions.Votes: 0GitHub stars: 2
- DebugSystematic 4-phase debugging methodology. Root cause investigation before any fixes. Read errors carefully, reproduce consistently, trace data flow, form hypotheses, test minimally. If 3+ fixes fail, question the architecture. No guessing, no quick patches, no symptom fixes.Votes: 0GitHub stars: 2
- PharaohWhich Pharaoh tool answers which structural question about a mapped repo (TypeScript, JavaScript, Python): where code lives, what calls it, what a change affects, what a module contains and what nothing runs. Use when Pharaoh's tools are connected and the question is about the structure of a repo Pharaoh maps.Votes: 0GitHub stars: 2
- PlanReview a plan or spec against the codebase before implementing it. Pharaoh reconnaissance, a BIG or SMALL change choice, then architecture, code quality, wiring, tests, performance and security sections with numbered decisions.Votes: 0GitHub stars: 2
- ReviewFive-phase code review: git context (branch, base, changed files), Pharaoh recon (architecture map, module context and blast radius, with a fallback when the repo isn't mapped), parallel specialized reviewers (correctness, security against the project's own rules, error handling, tests, types), an independent second-opinion pass for security-sensitive changes, and a SHIP / SHIP WITH CHANGES / BLOCK verdict. Architecture-aware wherever Pharaoh maps the repo. Use when reviewing a branch or pull...Votes: 0GitHub stars: 2
- TddTest-driven development discipline. Write the failing test first, watch it fail, write minimal code to pass, refactor. No production code without a failing test. No exceptions without explicit permission. Covers red-green-refactor cycle, common rationalizations, and when to start over.Votes: 0GitHub stars: 2
- VerifyEvidence before assertions. Run verification commands and confirm output before claiming work is complete, fixed, or passing. No 'should work now' — run the command, read the output, then claim the result. Covers tests, builds, linting, agent delegation, and requirement checklists.Votes: 0GitHub stars: 2