Problem

When I tag @claude in a GitHub issue to implement it with a PR, Claude doesn't have access to the knowledge base files that my local Claude Code automatically loads. This results in:

• Claude working without understanding our principles (tracer-bullets, versioning-mindset, OSE, etc.)
• Missing important procedures and workflows
• Lower quality PRs that don't follow established patterns
• Claude having to rediscover things that are already documented

Current State

• Local /close-issue command: Automatically loads ~30k tokens of context including:

  • Full knowledge/ directory with principles and procedures
  • CLAUDE.md and CLAUDE.local.md files
  • All INJECT patterns properly expanded

• @claude GitHub Action: Starts with zero context, must discover everything manually

Impact

The @claude workflow produces inferior results because it's essentially working blind. It doesn't know about:

• Our development principles
• Git workflow standards
• Worktree procedures
• Commit message conventions
• Any of the accumulated knowledge in the knowledge/ directory

Desired Outcome

The @claude GitHub Action should have the same knowledge context as the local /close-issue command, so it can produce equally high-quality PRs with proper understanding of our codebase patterns and principles.

Technical Context

• Current workflow uses anthropics/claude-code-action@beta which doesn't support custom prompts
• Alternative anthropics/claude-code-base-action@beta does support prompt injection
• Need to aggregate and inject knowledge files into the GitHub Action context