Commit Graph

29 Commits

Author SHA1 Message Date
Claude e45065e8ba docs: refresh README/docs/examples + install scripts for waves 1-4
User-facing documentation drifted behind several waves of feature work
(plugin manifest, hooks, sync command, --weekly, audit skills, Karpathy
skill, CLAUDE.local.md tier, layered hook config). Refresh + fix one
real install bug. Surgical edits only — no rewrites.

README.md:
  - "What's New" block now reflects the plugin manifest, --weekly,
    InstructionsLoaded hook, AGENTS.md interop, CLAUDE.local.md tier,
    layered hook config, and the fail-closed guardian.
  - "What's Included" expanded from 5 numbered bullets to a structured
    list grouping the 5 skills (incl. three forked audit skills),
    2 slash commands, 1 agent, and 3 hook scripts.
  - Components Deep Dive: /sync-claude-md and the guardian's fail-closed
    contract now documented.
  - Project Status: 1.0.0 -> 2.1.0; Quick Stats updated to reflect
    actual component counts.
  - Acknowledgments: attribution to MIT-licensed forrestchang and
    shanraisshan source repos for adapted patterns.

docs/ARCHITECTURE.md, docs/QUICK_START.md, docs/TROUBLESHOOTING.md,
docs/INSTALLATION.md, examples/modular-setup.md, examples/integration-
examples.md:
  - Every "20-300 lines" / ">300 lines" / "exceeds 300 lines" reference
    rewritten to the actual 150-line hard cap.
  - Every ls/Remove-Item path that pointed at the legacy
    ~/.claude/commands/enhance-claude-md/ bundle now points at the
    top-level enhance-claude-md.md + sync-claude-md.md files.
  - integration-examples.md line-bounds shell guard now uses 20..150.

docs/CLAUDE.md:
  - Install-verify ls list extended with the three new audit-skill
    directories so docs match what install.sh actually creates.

install.sh + install.ps1 (REAL FIX, not just docs):
  - The three forked audit skills (claude-md-drift-audit, link-check,
    dependency-rescan) were registered in plugin.json but never copied
    by the direct-install path. Both installers now iterate over them
    after the karpathy-guidelines block, mirroring the same backup +
    nested-duplicate-cleanup pattern. Banner section and uninstall
    instructions list all 5 skills.

Verified:
  - All 5 CLAUDE.md files in this repo still <= 150 lines after edits.
  - install.sh passes bash -n syntax check.
  - Plugin manifest still resolves all 8 referenced paths on disk.
  - README invariants present: 2.1.0, --weekly, hooks/hooks.json,
    both source-repo attributions, three audit skill names.
  - Stale-claim sweep: zero "20-300" / ">300" / "exceeds 300" refs
    remain in docs/ or examples/.
2026-05-19 02:04:00 +00:00
Claude 45767e8840 feat(skills): three forked task-style audit skills + /sync-claude-md --weekly orchestration
Three new task-style skills, each using Anthropic's context: fork + agent:
Explore so the work happens in an isolated subagent context and only a
short summary returns to the main session.

skill/claude-md-drift-audit/SKILL.md (51 lines):
  Walks the last N days of git history (default 7) and flags CLAUDE.md
  lines that reference deleted paths, renamed paths, or removed
  dependencies from that window. Returns a punch list with file:line.
  Read-only. Standalone invocation: /claude-md-drift-audit [days=7].

skill/claude-md-link-check/SKILL.md (51 lines):
  Verifies every @path chain import and every relative markdown link
  inside every CLAUDE.md resolves to an existing file. Returns broken
  links with file:line. Read-only. Standalone: /claude-md-link-check
  [path-glob].

skill/claude-md-dependency-rescan/SKILL.md (54 lines):
  Re-detects the project's tech stack from package.json /
  requirements.txt / pyproject.toml / go.mod / Cargo.toml and diffs
  against every CLAUDE.md's Tech Stack section. Returns added /
  removed / renamed per file. Read-only. Standalone:
  /claude-md-dependency-rescan [manifest-path].

command/sync-claude-md.md:
  - argument-hint and when_to_use mention --weekly.
  - New Phase 0 (only when --weekly is passed): invoke the three skills
    above in parallel via the Skill tool, aggregate findings into
    ## Weekly Audit Summary, then proceed to existing Phase 1.
  - Without --weekly, Phase 0 is skipped entirely (no behaviour change
    for normal sync runs).

.claude-plugin/plugin.json:
  skills array now lists all five entries (existing two + three new).

Verified (6/6 smoke tests):
  - Plugin manifest is valid JSON; 5 skills registered; all 8
    referenced paths resolve on disk.
  - Each new SKILL.md parses; context=fork, agent=Explore, both
    description and when_to_use present, allowed-tools is a list,
    body ≤ 60 lines.
  - Each body is imperative (numbered steps present, not reference
    material — fork-context requires explicit task instructions).
  - Sync command body contains Phase 0, all three skill references,
    parallel-invocation language, and Skill in allowed-tools.
  - Skill name in frontmatter matches the directory name for every
    new skill (so /claude-md-drift-audit etc. register correctly).
2026-05-19 02:04:00 +00:00
Claude e33fa8326b feat(plugin): command metadata, scoped skills, local-tier support, layered hooks, Stop audit
Wave 3 - adoption hardening. Patterns adapted (in original prose, with
attribution) from MIT-licensed shanraisshan/claude-code-best-practice.

Commands (command/enhance-claude-md.md, command/sync-claude-md.md):
- Add allowed-tools / disallowedTools / argument-hint / when_to_use so the
  commands auto-suggest in the slash menu and avoid permission prompts.
- disallowedTools blocks WebFetch + WebSearch on both commands.
- Drop the previous broken hooks block (array-of-{matcher, commands} shape
  did not match canonical schema; was never firing).

Skills:
- skill/karpathy-guidelines/SKILL.md: paths: glob over 23 code-file
  extensions, so the guardrails auto-load only when editing source, not
  markdown or data.
- skill/SKILL.md: model: haiku, effort: medium, paths: scoped to CLAUDE.md
  + AGENTS.md + .claude/rules/*.md so validator/generator passes run
  cheaply without changing the user-facing model.

CLAUDE.local.md personal tier:
- skill/validator.py BestPracticesValidator now accepts filename=; any
  *.local.md basename waives the 150-line cap.
- hooks/validate-claude-md.py reads the exempt suffix from hooks-config.
- .gitignore covers CLAUDE.local.md, **/CLAUDE.local.md,
  .claude/settings.local.json, hooks/hooks-config.local.json.

Layered hook config:
- hooks/hooks-config.json: committed defaults
  (validateClaudeMd.enabled/maxLines/exemptFilenameSuffix/exitCodeOnViolation,
  stopAuditLine.enabled).
- hooks/validate-claude-md.py merges hooks-config.json +
  hooks-config.local.json key-by-key; honours enabled=false (silent
  exit 0), configurable cap, configurable exit code.

Stop audit hook:
- hooks/audit-claude-md.py walks the project tree, prints one stderr
  line: total tracked / OVER cap / near cap (>=80%). Respects
  stopAuditLine.enabled from config.
- hooks/hooks.json registers Stop event with matcher "".

Guardian fail-closed contract:
- agent/claude-md-guardian.md Safety & Validation section now explicitly
  requires Skill-tool invocation (no inline paraphrase of SKILL.md),
  abort on missing validated output, never auto-commit, and respect
  local hook config.

Verified (8/8 smoke tests):
- Both commands parse with new fields and no broken hooks block.
- karpathy paths: 23 globs, includes .py/.ts/.go/.rs.
- skill model=haiku effort=medium with CLAUDE.md path scope.
- Validator: *.local.md (300 lines) -> pass; CLAUDE.md (300) -> fail;
  legacy ctor without filename -> default behavior preserved.
- hooks-config.json valid; validateClaudeMd.enabled=true, maxLines=150.
- Hook validator: default rc=2 on bloated, rc=0 when local override
  disables it, rc=0 on *.local.md (exempt).
- Stop hook entry present; audit script: rc=0 with "5 CLAUDE.md tracked".
- Regression: large-fullstack root still 52 lines with chain imports.
2026-05-19 02:04:00 +00:00
Claude 0a34178e22 feat(plugin): fix guardian hooks, add InstructionsLoaded enforcement, .claude/rules emitter, AGENTS.md interop
Closes the gap between ClaudeForge and the Anthropic docs at
code.claude.com/docs/en/memory (and its linked hooks / skills / plugins
pages). Five tightly-scoped changes, each verified by smoke test.

A. Fix guardian hook frontmatter shape (agent/claude-md-guardian.md)

   The previous array-of-{event, commands} shape did not match the
   documented schema (hooks: { EventName: [{ matcher, hooks: [{ type,
   command }] }] }), so the guardian's hooks silently did not fire.
   Rewritten to the canonical keyed-object shape with PostToolUse,
   PreToolUse, SessionStart, and the new InstructionsLoaded event.

B+C. Plugin-level hooks/hooks.json + hooks/validate-claude-md.py

   New deterministic enforcement of the 150-line cap. The validator
   script reads the hook payload from stdin, extracts any referenced
   CLAUDE.md path (supports both PostToolUse tool_input.file_path and
   InstructionsLoaded path / file shapes), and exits 2 with stderr
   feedback when the file is over 150 lines. Wired to both PostToolUse
   on Write|Edit and InstructionsLoaded on every load_reason
   (session_start, nested_traversal, path_glob_match, include, compact).
   The cap is now enforced at every load *and* write, not only when the
   guardian decides to run sync.

D. ContentGenerator.generate_rules_file() (skill/generator.py)

   Emits path-scoped .claude/rules/*.md instruction files with name,
   description, and paths: glob frontmatter. Claude loads these
   lazily — only when accessing files matching the globs — so
   file-type-specific guidance no longer has to live in the root
   CLAUDE.md. Validates that paths is non-empty (ValueError otherwise).

E. AGENTS.md / .cursorrules / .windsurfrules interop

   command/enhance-claude-md.md Phase 1 now lists which sibling
   instruction files exist. ContentGenerator.generate_root_file() reads
   project_context['existing_instruction_files'] and prepends an
   ## External Instructions section with @AGENTS.md (etc.) imports, so
   repos already using other agent tooling can adopt ClaudeForge
   without losing their existing instructions.

Smoke tests (all pass):
- Guardian hooks frontmatter parses as a dict with 4 events, each
  carrying matcher + nested hooks array of {type, command} entries.
- hooks.json is valid JSON; PostToolUse matcher = Write|Edit;
  InstructionsLoaded matcher covers all five load_reason values.
- validate-claude-md.py: small file -> rc 0, bloated file (200 lines)
  -> rc 2 with stderr referencing the 150 cap, InstructionsLoaded
  payload shape also handled, non-CLAUDE.md paths ignored, no stdin
  -> rc 0.
- generate_rules_file emits valid frontmatter with paths glob and
  raises ValueError when paths is empty.
- generate_root_file inserts @AGENTS.md and @.cursorrules imports
  when existing_instruction_files lists them; omits the section
  otherwise.
- Regression: large-fullstack root still 52 lines with chain imports
  intact; all five sub-CLAUDE.md files in this repo still pass
  validator (status = pass).

Docs:
- agent/CLAUDE.md updated to show the canonical hook shape and the
  hook-driven validator wiring.
- skill/CLAUDE.md notes generate_rules_file and AGENTS.md interop.
- CHANGELOG.md documents all five changes under Unreleased.
2026-05-19 02:04:00 +00:00
Claude c374cc28a1 docs(claude-md): dogfood /sync-claude-md on root CLAUDE.md
Splits the 518-line root CLAUDE.md into a 70-line root plus four chained
sub-files (skill/, command/, agent/, docs/), all under the 150-line cap,
and prunes stale references uncovered by the audit.

- CLAUDE.md (518 -> 70): project overview, navigation with @-imports,
  behavioural guidelines summary, naming reference, license link
- skill/CLAUDE.md (85): component flow, Python module architecture,
  modifying modules, adding templates, tech-stack detection, quality
  scoring, karpathy skill
- command/CLAUDE.md (38): slash command development, top-level .md install
  layout, skill <-> command integration
- agent/CLAUDE.md (70): guardian frontmatter, hook responsibilities,
  skill <-> agent integration, git triggers
- docs/CLAUDE.md (109): install verification, smoke test, manual e2e
  tests, common operations, release process

Stale content removed:
- 'Dual Directory Structure' section (claude-md-enhancer/ legacy dir
  does not exist on disk)
- '20-300 lines' / '300-line cap' references rewritten to 150
- '~/.claude/commands/enhance-claude-md/' bundle paths rewritten to
  top-level '.md' files (matching the new installer layout)
- 'Three integrated components' updated to five
- 'Current Version: 2.0.0' updated to 2.1.0
- '6 examples' in sample_input.json claim corrected (file has 1 scenario)

Each sub-file opens with a markdown back-link and @../CLAUDE.md import;
root contains @-imports for all four sub-files. Validator passes (status
pass) for every file.
2026-05-19 02:04:00 +00:00
Claude a45e6f5dbd feat(plugin): ship as Claude Code plugin with 150-line cap and sync command
Turns ClaudeForge into an installable Claude Code plugin and adds the
missing pieces for a clean lifecycle: hard line-cap enforcement, modular
chaining via @path imports, a sync/cleanup command, and Explore-agent
delegation for project discovery.

- .claude-plugin/plugin.json: plugin manifest registering both skills,
  both commands, and the guardian agent (installable via /plugin marketplace
  add alirezarezvani/ClaudeForge && /plugin install claudeforge)
- skill/validator.py: MAX_RECOMMENDED_LINES 300 -> 150 (warning at 120)
- skill/template_selector.py: target_lines capped at 150 across all
  team sizes (solo 75 / small 100 / medium 125 / large 150) so any
  single CLAUDE.md fits within the cap; bigger projects spread content
  across modular sub-files
- skill/analyzer.py: length thresholds, quality scoring, and recommendations
  rebased on the 150 cap (was 300/400)
- skill/generator.py: modular root now emits @path imports next to the
  human-readable links; every sub-CLAUDE.md gets a back-link header
  pointing to ../CLAUDE.md (markdown + @import) for bidirectional chaining
- command/sync-claude-md.md: new /sync-claude-md command that inventories
  every CLAUDE.md, prunes stale references, enforces the 150 cap by
  splitting into sub-files, and repairs the root <-> sub chain
- command/enhance-claude-md.md: discovery phase now delegates the deep
  codebase scan to the Explore subagent to keep context lean
- install.sh / install.ps1: each command in command/ installs as its own
  ~/.claude/commands/<name>.md (legacy bundle backed up on upgrade)
- skill/SKILL.md, CLAUDE.md, README.md, CHANGELOG.md: docs updated for
  the plugin install path, sync command, and new line cap

Verified via smoke test: validator constants, template targets, generator
output line counts across 5 presets (all <= 150), context files with
backlinks, @-import chain in modular root, idempotent merge_with_existing,
validator status transitions at the new cap, analyzer quality differential,
and plugin manifest JSON shape with all referenced paths existing on disk.
2026-05-19 02:03:59 +00:00
Alireza Rezvani ffff0fc4c3 feat(skill): integrate Karpathy behavioral guidelines into every CLAUDE.md (#25) 2026-05-19 01:55:12 +02:00
Alireza Rezvani e7512689c1 feat(v2.0.0): migrate to Claude Code v2.1.4+ architecture (#22) 2026-02-16 00:36:41 +01:00
Alireza Rezvani f52664867d chore(sync): merge main into dev to align branches (#20)
* fix(ci): add missing PR template enhancements

- Add CI/CD workflow change type
- Expand checklist with quality gates sections
- Add Conventional Commits and branch naming reminders
- Better organize code quality, docs, testing, CI/CD sections

This file was modified in Phase 2 but accidentally not staged.

* docs: add comprehensive CI/CD and branching documentation

Phase 3: Documentation & Branch Setup

Created Documentation (1200+ lines):
- GITHUB_WORKFLOWS.md: Complete reference for all 5 workflows and 4 composite actions
  - Detailed explanations of bootstrap, pr-into-dev, dev-to-main, release workflows
  - Quality gates documentation (Python, Markdown, Bash, secrets)
  - Troubleshooting guide for common workflow issues
  - Configuration examples and customization options

- BRANCHING_STRATEGY.md: Standard branching model documentation
  - feature/* → dev → main flow explained
  - Branch protection configuration guide
  - Conventional Commits format with examples
  - Git commands cheat sheet
  - Common scenarios and best practices
  - Merge strategy (squash merges)

Updated README.md:
- Added CI/CD and Quality Gates badges
- Added links to new workflow and branching docs
- Better documentation table organization

Branch Setup:
- Created and pushed dev branch
- Ready for branch protection configuration

Next: Phase 4 (Claude Code slash commands for GitHub workflows)

* feat(commands): add GitHub workflow integration slash commands

Phase 4: Claude Code Slash Commands

Created 4 GitHub Integration Commands:

1. /github-init - CI/CD system initialization
   - Runs bootstrap workflow
   - Creates dev branch
   - Configures branch protection
   - Sets default branch to dev
   - Complete setup verification

2. /commit-smart - Smart commits with quality gates
   - Pre-commit validation (Python, Bash, secrets)
   - Conventional Commits format generation
   - Interactive commit message builder
   - Quality checks before committing

3. /create-pr - Pull request creation
   - Branch validation
   - Target branch detection (dev/main)
   - PR title generation (Conventional Commits)
   - PR template population
   - Workflow trigger explanation

4. /release - GitHub release creation
   - Version validation (semantic versioning)
   - CHANGELOG.md integration
   - Automated release notes
   - Post-release actions guide

All commands provide:
- Step-by-step guidance
- Copy-paste ready commands
- Validation checks
- Error handling
- Links to documentation

Integration with workflows:
- Commands trigger bootstrap, pr-into-dev, dev-to-main, release workflows
- Enforces quality gates and conventions
- Aligns with branching strategy

Next: Test workflows with sample feature PR

* fix(ci): handle multi-line PR body in linked issues check

Use heredoc to safely write PR body to temp file instead of storing in variable.
This prevents bash from interpreting special characters and multi-line content
as commands (exit code 127 error).

Fixes workflow failure in PR #3.

* fix(ci): skip interactive scripts in bash syntax validation

Interactive scripts that use /dev/tty for user input trigger false positives
in bash -n syntax checking. This change:

- Excludes install.sh from bash validation
- Skips any script containing /dev/tty
- Fixes quality gates failure in PR workflows

Resolves quality gates failure in PR #5.

* release: CI/CD system v1.1.0

* fix(ci): handle multi-line PR body in linked issues check

Use heredoc to safely write PR body to temp file instead of storing in variable.
This prevents bash from interpreting special characters and multi-line content
as commands (exit code 127 error).

Fixes workflow failure in PR #3.

* fix(ci): skip interactive scripts in bash syntax validation

Interactive scripts that use /dev/tty for user input trigger false positives
in bash -n syntax checking. This change:

- Excludes install.sh from bash validation
- Skips any script containing /dev/tty
- Fixes quality gates failure in PR workflows

Resolves quality gates failure in PR #5.

* feat(docs): validate multi-line PR body fix in workflows (#5)

* feat(docs): add CI/CD fix validation documentation

* chore: trigger workflow with updated quality gates

* fix(ci): exclude docs from secret scanning and skip interactive script validation

- Security checks: Exclude docs/ and examples/ from secret pattern matching
  (prevents false positives on documentation examples)
- Install validation: Skip bash -n check for scripts using /dev/tty
  (interactive scripts are valid but fail non-interactive syntax checking)

Fixes workflow failures in dev-to-main PRs.

* fix(ci): skip bash -n check for install.sh in validate workflow

Interactive script with /dev/tty cannot be syntax-checked non-interactively.

* chore(release): merge dev into main - CI fixes and workflow improvements (#16)

* fix(ci): handle multi-line PR body in linked issues check

Use heredoc to safely write PR body to temp file instead of storing in variable.
This prevents bash from interpreting special characters and multi-line content
as commands (exit code 127 error).

Fixes workflow failure in PR #3.

* fix(ci): skip interactive scripts in bash syntax validation

Interactive scripts that use /dev/tty for user input trigger false positives
in bash -n syntax checking. This change:

- Excludes install.sh from bash validation
- Skips any script containing /dev/tty
- Fixes quality gates failure in PR workflows

Resolves quality gates failure in PR #5.

* feat(docs): validate multi-line PR body fix in workflows (#5)

* feat(docs): add CI/CD fix validation documentation

* chore: trigger workflow with updated quality gates

* fix(ci): exclude docs from secret scanning and skip interactive script validation

- Security checks: Exclude docs/ and examples/ from secret pattern matching
  (prevents false positives on documentation examples)
- Install validation: Skip bash -n check for scripts using /dev/tty
  (interactive scripts are valid but fail non-interactive syntax checking)

Fixes workflow failures in dev-to-main PRs.

* fix(ci): skip bash -n check for install.sh in validate workflow

Interactive script with /dev/tty cannot be syntax-checked non-interactively.
2026-01-07 18:00:46 +01:00
Alireza Rezvani e684e90e09 fix(installer): resolve bash syntax error in read commands (#19)
Fixed bash syntax error caused by missing quotes around color variables
in command substitution within read -p commands.

Changes:
- Line 132: Added quotes around ${BLUE} and ${NC} in installation prompt
- Line 179: Added quotes around ${BLUE} and ${NC} in hooks prompt

This prevents "syntax error near unexpected token" errors during
installation on macOS and other systems.

Fixes #13

Credit: Original fix by @bartdorlandt in PR #14

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
Co-authored-by: Bart Dorlandt <bartdorlandt@users.noreply.github.com>
2026-01-07 17:53:07 +01:00
Alireza Rezvani abd2aa319a docs(changelog): add entry for install.sh quote fix (#13) (#15)
* docs(changelog): add entry for install.sh quote fix (#13)

Added CHANGELOG entry for bash syntax error fix in install.sh.
Documented the quote fix for color variables in read commands.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>

* docs(changelog): add entry for branch naming requirement removal

Updated CHANGELOG to document the removal of strict branch naming
validation from PR workflow.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
2026-01-07 17:47:55 +01:00
Alireza Rezvani 77cac6ffd6 fix(ci): remove branch naming requirement for PRs into dev (#17)
Removed strict branch naming validation that was blocking PRs.
Contributors can now use any branch name when creating PRs into dev.

Changes:
- Removed "Validate branch name" step from pr-into-dev workflow
- Updated error comment script to remove branch name references
- Kept PR title validation (Conventional Commits) and linked issues check

Rationale: Branch naming requirements add unnecessary friction for
contributors without significant benefit. PR title validation provides
sufficient commit message hygiene.

Fixes validation failure in PR #14 and future contributor PRs.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Sonnet 4.5 (1M context) <noreply@anthropic.com>
2026-01-07 17:47:45 +01:00
Reza Rezvani 776220f441 fix(ci): skip bash -n check for install.sh in validate workflow
Interactive script with /dev/tty cannot be syntax-checked non-interactively.
2025-11-12 15:22:33 +01:00
Reza Rezvani 2307f06221 fix(ci): exclude docs from secret scanning and skip interactive script validation
- Security checks: Exclude docs/ and examples/ from secret pattern matching
  (prevents false positives on documentation examples)
- Install validation: Skip bash -n check for scripts using /dev/tty
  (interactive scripts are valid but fail non-interactive syntax checking)

Fixes workflow failures in dev-to-main PRs.
2025-11-12 15:18:55 +01:00
Alireza Rezvani c7b77399a8 feat(docs): validate multi-line PR body fix in workflows (#5)
* feat(docs): add CI/CD fix validation documentation

* chore: trigger workflow with updated quality gates
2025-11-12 15:08:53 +01:00
Reza Rezvani 6b542d1554 fix(ci): skip interactive scripts in bash syntax validation
Interactive scripts that use /dev/tty for user input trigger false positives
in bash -n syntax checking. This change:

- Excludes install.sh from bash validation
- Skips any script containing /dev/tty
- Fixes quality gates failure in PR workflows

Resolves quality gates failure in PR #5.
2025-11-12 14:37:35 +01:00
Reza Rezvani ad03dea942 fix(ci): handle multi-line PR body in linked issues check
Use heredoc to safely write PR body to temp file instead of storing in variable.
This prevents bash from interpreting special characters and multi-line content
as commands (exit code 127 error).

Fixes workflow failure in PR #3.
2025-11-12 14:33:32 +01:00
Alireza Rezvani 80e4588f81 Merge pull request #3 from alirezarezvani/feature/test-ci-workflow
feat(docs): add CI/CD workflow testing documentation
2025-11-12 13:44:12 +01:00
Reza Rezvani 582a116f72 feat(docs): add CI/CD workflow testing documentation
Add test documentation to validate the CI/CD workflows are
functioning correctly. This PR will test:

- Branch name validation (feature/* pattern)
- PR title validation (Conventional Commits)
- Quality gates (Markdown linting, secret scanning)
- pr-into-dev.yml workflow execution

This is a test PR to ensure all GitHub Actions workflows
are properly configured and executing as expected.
2025-11-12 13:07:50 +01:00
Reza Rezvani 2651797190 feat(ci): enhance GitHub templates and add configuration files
Phase 2: GitHub Templates & Configuration

Issue Templates:
- Enhanced bug_report.md with Python version and component fields
- Added 'needs discussion' label to feature_request.md for better triage

PR Template:
- Added CI/CD workflow change type
- Expanded checklist with quality gates, documentation, testing, and CI/CD sections
- Added Conventional Commits reminder and branch naming convention
- Better organized sections for code quality, docs, testing

Configuration Files:
- CODEOWNERS: Auto-request review from @alirezarezvani for critical paths
- commit-template.txt: Conventional Commits guide with examples
- dependabot.yml: Weekly Python (pip) and GitHub Actions dependency updates

Aligns templates with new CI/CD workflows from Phase 1:
- PR validation expects Conventional Commits format
- Quality gates check Python, Markdown, Bash, secrets
- Branch naming conventions enforced by pr-into-dev workflow

Next: Phase 3 (dev branch creation, branch protection documentation)
2025-11-12 12:54:03 +01:00
Reza Rezvani dd6a6c24d7 feat(ci): implement comprehensive CI/CD workflows and quality gates
Phase 1: Core GitHub Workflows Implementation

Composite Actions (4):
- setup-python-deps: Cache Python dependencies for faster runs
- fork-safety: Detect fork PRs and prevent malicious write operations
- rate-limit-check: Circuit breaker pattern for GitHub API exhaustion
- quality-gates: Python syntax, Markdown lint, Bash validation, secret scanning

Workflows (5):
- bootstrap.yml: One-time repository setup (labels, milestones, settings)
- reusable-pr-checks.yml: DRY quality gate orchestrator
- pr-into-dev.yml: Feature PR validation (branch names, conventional commits, linked issues)
- dev-to-main.yml: Release gate validation (source branch, CHANGELOG, production readiness)
- release.yml: Manual release creation with GitHub releases and auto-generated notes

Branch Strategy: Standard (feature/* → dev → main)
Quality Gates: Python, Markdown, Bash, Secrets
Release Trigger: Manual via /release command or workflow_dispatch

Implements comprehensive CI/CD system adapted from blueprint:
- Fork safety and rate limiting for security
- Conventional commits enforcement
- Automated quality validation
- Production release gates
- GitHub release automation

Next: Phase 2 (templates, CODEOWNERS, dependabot)
2025-11-12 12:51:48 +01:00
Reza Rezvani eea0f09753 fix(installer): Project-level installation now works correctly with remote install
CRITICAL FIX:
- Save original directory before downloading from GitHub
- For project-level installation via curl/remote, install to original directory
- Prevents .claude/ folder from being created in temp directory and deleted
- Fixes both bash (install.sh) and PowerShell (install.ps1) installers
- Quality hooks also install to correct directory

Before: curl | bash with option 2 would install to temp dir and delete it
After: curl | bash with option 2 installs to directory where command was run

This fixes the issue where users couldn't see .claude/ after installation.
2025-11-12 12:19:55 +01:00
Reza Rezvani 5ad6a1e0a7 fix(installer): Display colors correctly in all echo statements
- Added -e flag to all echo commands using color variables
- Fixes raw ANSI escape codes showing instead of colored text
- Improves user experience during installation
- Affects menu options, next steps, and documentation links
2025-11-12 12:13:07 +01:00
Reza Rezvani d5da9aeedb fix(installer): Read user input from /dev/tty for piped execution
- Fixed infinite loop when running via curl | bash
- All interactive prompts now read from /dev/tty instead of stdin
- Fixes installation choice, confirmation, and quality hooks prompts
- Ensures user input works correctly when script is piped through bash
2025-11-12 12:00:10 +01:00
Alireza Rezvani 8740f7c205 Merge pull request #1 from alirezarezvani/add-claude-github-actions-1762944570174
Add Claude Code GitHub Workflow
2025-11-12 11:49:44 +01:00
Alireza Rezvani b1884c428f "Claude Code Review workflow" 2025-11-12 11:49:32 +01:00
Alireza Rezvani 60dd6d9f5f "Claude PR Assistant workflow" 2025-11-12 11:49:31 +01:00
Reza Rezvani b8f12f34f7 fix(installers): Enable one-line installation from curl/web
- Add automatic download from GitHub when files not present locally
- Support both local and remote installation modes
- Download v1.0.0 release tarball/zip automatically
- Clean up temporary files after remote installation
- Update both install.sh (macOS/Linux) and install.ps1 (Windows)

Now the one-line install works correctly:
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/ClaudeForge/main/install.sh | bash

Fixes #1 (if issue exists)
2025-11-12 11:45:57 +01:00
Reza Rezvani 37422c1667 Initial commit: ClaudeForge v1.0.0 v1.0.0 2025-11-12 11:19:48 +01:00