Claude Code instructions for GabsFranke/claude-code-github-agent, covering agent instructions for claude code github agent, where you are, architecture overview, technology stack and code quality standards.
Comprehensive CI/CD failure analysis and fix toolkit with specialized agents for build failures, test failures, linting issues, and deployment problems.
Specialist in diagnosing and fixing build failures, compilation errors, dependency issues, and configuration problems. Use proactively when CI builds fail.
Specialist in diagnosing and fixing deployment failures, Docker build issues, container problems, and health check failures. Use proactively when CI deployment fails.
Use this agent when reviewing a pull request for architectural concerns including component coupling, dependency direction, separation of concerns, module boundaries, API design, and consistency with existing codebase patterns. This agent should be run for most non-trivial PRs alongside code-reviewer. It uses codebase…
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best…
Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes: (1) After generating large documentation comments or docstrings, (2) Before finalizing a pull request that adds or modifies comments, (3) When reviewing existing comments for potential…
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could…
Use this agent when you need expert analysis of type design in your codebase. Specifically use it: (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, (3) when refactoring existing types to…
Analyses completed agent session transcripts for failures and missed opportunities, then proposes targeted improvements to agent instructions via a PR to develop.
Use this agent when the test-toolkit skill needs to delegate work to a subagent. This agent executes any generic task it receives — reading files, running commands, writing code, searching — and returns results. It is used to verify that tools and configuration properly inherit from the parent plugin to subagents.
Use this skill whenever you need to explore, search, or understand code — including code reviews, PR analysis, architecture review, finding definitions or references, tracing call graphs and dependencies, assessing the impact of changes, discovering API routes or MCP tools, searching by concept, or understanding file…