Add comprehensive GitHub Actions CI/CD pipeline for Elisp, Org-mode, and JavaScript testing

[Copilot]

Implements a production-grade CI/CD pipeline with 14 workflows covering code quality, compilation, testing, security, and release automation for the emacs-aichat-skintwin cognitive architecture system.

Workflows

Core CI (7)

• elisp-lint.yml - checkdoc, package-lint, encoding validation
• elisp-compile.yml - byte-compilation across Emacs 27.2/28.2/29.1
• elisp-test.yml - ERT tests, OpenCog/SkinTwin module verification
• org-mode-validation.yml - syntax, structure, link validation, HTML export
• javascript-ci.yml - Vite build, Vitest tests on Node 18.x/20.x
• ci-pipeline.yml - orchestrates pre-checks and validation
• test.yml - legacy compatibility layer

Quality & Security (3)

• code-quality.yml - complexity analysis, naming conventions, dependency checks
• documentation-check.yml - README/CHANGELOG validation, spell check, version consistency
• security-scan.yml - CodeQL, TruffleHog secret scanning, npm audit, Elisp pattern detection

Automation (3)

• dependency-updates.yml - weekly npm/Cask updates with auto-PR
• nightly-build.yml - cross-platform builds (Ubuntu/macOS)
• performance-tests.yml - AtomSpace, ECAN, PLN benchmarks with configurable regression thresholds

Release (1)

• release.yml - automated GitHub releases on version tags

Key Features

• Matrix testing: 3 Emacs versions × 2 Node versions
• Scheduled: daily security/nightly (2 AM UTC), weekly deps/perf (Mon 9 AM, Sun 12 AM UTC)
• Configurable performance thresholds via environment variables
• Strategic artifact retention (7-90 days)
• Extracted performance tests to .github/scripts/run-performance-tests.sh for maintainability

Example: Performance Benchmarking

- name: Run performance benchmarks
  run: .github/scripts/run-performance-tests.sh
  env:
    PERFORMANCE_THRESHOLD: "5.0"  # Configurable regression threshold

The script benchmarks AtomSpace operations, ECAN spreading, PLN reasoning, and detects performance regressions above the configured threshold.

Documentation

• README.md - workflow reference with trigger matrices
• TESTING.md - troubleshooting guide
• QUICKREF.md - command cheat sheet
• IMPLEMENTATION.md - technical summary

All workflows validated with proper YAML syntax, error handling, and artifact management.

Original prompt

create a comprehensive suite of github action workflows to imlement & test the emacs-aichat-skintwin system repo with all stages of development relevant to code quality, compiling and execution of elisp & org-mode features and functions

Custom agent used: emacs-aichat-skintwin
OpenCog-based dermatological cognitive system for Emacs with AI chat integration

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[drzo]

cooool

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.