fix: inject ~30k token knowledge base into @claude GitHub Actions (documentation as code) #1185
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,28 +1,4 @@ | ||
| # Close Issue Command Template | ||
| Complete and implement GitHub issue #{{ ISSUE_NUMBER }}. | ||
|
|
||
| {{ INJECT:knowledge/procedures/close-issue-procedure.md }} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,103 @@ | ||
| #!/bin/bash | ||
| # Aggregate knowledge base for GitHub Actions | ||
| # This script reads ALL knowledge files (matching Claude Code's behavior) | ||
| # and outputs them as a single text block for injection into Claude's prompt | ||
| # Principle: systems-stewardship | ||
|
|
||
| set -euo pipefail | ||
|
|
||
| # Get the repository root (two levels up from .github/scripts) | ||
| REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)" | ||
| KNOWLEDGE_DIR="$REPO_ROOT/knowledge" | ||
|
|
||
| # Start with a header | ||
| echo "# Knowledge Base Context" | ||
| echo "" | ||
| echo "This context is automatically injected to provide Claude with understanding of:" | ||
| echo "- Core development principles and procedures" | ||
| echo "- Personality models for retrospectives" | ||
| echo "- System architecture patterns and tools" | ||
| echo "- The North Star throughput definition" | ||
| echo "" | ||
|
|
||
| # Note: CLAUDE.md is not included here as it's a user-specific file | ||
| # that lives in ~/.claude/CLAUDE.md (not in the repository). | ||
| # GitHub Actions only has access to committed repository files. | ||
|
|
||
| # Process all .md files in knowledge/ recursively to match Claude Code behavior | ||
| # This ensures GitHub Actions has the exact same context as local development | ||
| process_directory() { | ||
| local dir="$1" | ||
| local relative_path="${dir#$KNOWLEDGE_DIR}" | ||
| relative_path="${relative_path#/}" # Remove leading slash if present | ||
|
|
||
| # Process files in current directory first | ||
| for file in "$dir"/*.md; do | ||
| if [[ -f "$file" ]]; then | ||
| filename=$(basename "$file" .md) | ||
|
|
||
| # Skip README files in subdirectories (but include the main one) | ||
| if [[ "$filename" == "README" && "$relative_path" != "" ]]; then | ||
| continue | ||
| fi | ||
|
|
||
| # Create section header based on location | ||
| if [[ "$relative_path" == "" ]]; then | ||
| # Root knowledge files | ||
| title=$(echo "$filename" | sed 's/-/ /g' | sed 's/\b\(.\)/\u\1/g') | ||
| echo "# $title" | ||
| elif [[ "$relative_path" == "principles" ]]; then | ||
| title=$(echo "$filename" | sed 's/-/ /g' | sed 's/\b\(.\)/\u\1/g') | ||
| echo "## Principle: $title" | ||
| elif [[ "$relative_path" == "procedures" ]]; then | ||
| title=$(echo "$filename" | sed 's/-/ /g' | sed 's/\b\(.\)/\u\1/g') | ||
| echo "## Procedure: $title" | ||
| elif [[ "$relative_path" == "personalities" ]]; then | ||
| title=$(echo "$filename" | sed 's/-/ /g' | sed 's/\b\(.\)/\u\1/g') | ||
| echo "## Personality: $title" | ||
| elif [[ "$relative_path" == "tools" ]]; then | ||
| title=$(echo "$filename" | sed 's/-/ /g' | sed 's/\b\(.\)/\u\1/g') | ||
| echo "## Tool: $title" | ||
| else | ||
| # Other directories | ||
| title=$(echo "$filename" | sed 's/-/ /g' | sed 's/\b\(.\)/\u\1/g') | ||
| echo "## $relative_path: $title" | ||
| fi | ||
|
|
||
| echo "" | ||
| cat "$file" | ||
| echo "" | ||
| echo "---" | ||
| echo "" | ||
| fi | ||
| done | ||
|
|
||
| # Process subdirectories | ||
| for subdir in "$dir"/*; do | ||
| if [[ -d "$subdir" ]]; then | ||
| dirname=$(basename "$subdir") | ||
| # Add section header for new directory | ||
| if [[ "$relative_path" == "" ]]; then | ||
| echo "# $(echo "$dirname" | sed 's/\b\(.\)/\u\1/g')" | ||
| echo "" | ||
| fi | ||
| process_directory "$subdir" | ||
| fi | ||
| done | ||
|
atxtechbro marked this conversation as resolved.
|
||
| } | ||
|
|
||
| # Process the entire knowledge directory | ||
| if [[ -d "$KNOWLEDGE_DIR" ]]; then | ||
| process_directory "$KNOWLEDGE_DIR" | ||
| else | ||
| echo "Knowledge directory not found at: $KNOWLEDGE_DIR" | ||
| echo "" | ||
| fi | ||
|
|
||
| # Add a footer note | ||
| echo "" | ||
| echo "# Context Note" | ||
| echo "" | ||
| echo "This knowledge base was automatically aggregated for this GitHub Action workflow." | ||
| echo "Follow these principles and procedures to maintain consistency with the codebase patterns." | ||
| echo "Reference: Principles are in knowledge/principles/, Procedures are in knowledge/procedures/" | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,47 @@ | ||
| # Close Issue Procedure | ||
| # | ||
| # This IS the implementation - the procedure documents itself by being the code. | ||
| # Used by both: | ||
| # - Local /close-issue command (via relative path injection) | ||
| # - GitHub Actions @claude workflow (with knowledge base injection) | ||
| # | ||
| # IMPORTANT: How {{ KNOWLEDGE_BASE }} works: | ||
| # - For GitHub Actions: Gets replaced with aggregated knowledge files via string substitution | ||
| # - For local /close-issue: Remains as literal text "{{ KNOWLEDGE_BASE }}" in the prompt | ||
| # (harmless since knowledge is already preloaded in Claude's context) | ||
| # | ||
| # This is NOT smart placeholder logic - it's simple: | ||
| # - GitHub Actions: Does string replacement: {{ KNOWLEDGE_BASE }} → actual content | ||
| # - Local command: Does NO replacement: {{ KNOWLEDGE_BASE }} → stays as literal text | ||
| # | ||
| # Principle: systems-stewardship (single source of truth, documentation as code) | ||
|
|
||
| Complete and implement GitHub issue #{{ ISSUE_NUMBER }}. | ||
|
|
||
| {{ KNOWLEDGE_BASE }} | ||
| <!-- Note: If you see "{{ KNOWLEDGE_BASE }}" above as literal text, you're running locally and knowledge is already preloaded --> | ||
|
|
||
| ## Core Principle: Target-First Development | ||
| {{ INJECT:principles/tracer-bullets.md }} | ||
|
|
||
| ## Analyze Issue #{{ ISSUE_NUMBER }} | ||
| <!-- This procedure IS the implementation - executable documentation --> | ||
| First, use `mcp__github__get_issue` to understand the issue and determine the appropriate workflow path. | ||
|
|
||
| ## Apply to Issue #{{ ISSUE_NUMBER }} | ||
| When following the procedure: | ||
| - Use issue #{{ ISSUE_NUMBER }} for all GitHub API calls | ||
| - Replace <NUMBER> with {{ ISSUE_NUMBER }} in branch names | ||
| - Replace <description> with issue title slug | ||
| - Reference "Closes #{{ ISSUE_NUMBER }}" in PR body | ||
|
|
||
| ## Final Step: Retro | ||
| Let's retro this context and wring out the gleanings. | ||
|
|
||
| {{ INJECT:principles/eager-evolution.md }} | ||
|
|
||
| **Consider capturing any ghost procedures** that emerged during this work - see [Procedure Creation](knowledge/procedures/procedure-creation.md). | ||
|
|
||
| **What would you like to focus on?** | ||
| - Do you have a specific aspect you want to double-click on? | ||
| - Or would you like me to suggest the top 3 areas I predict you'll find most valuable to explore? |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.