Skip to content

feat: add refined-github-projects ECC bundle - #64

Open
ecc-tools[bot] wants to merge 12 commits into
mainfrom
ecc-tools/refined-github-projects-1781444461944
Open

feat: add refined-github-projects ECC bundle#64
ecc-tools[bot] wants to merge 12 commits into
mainfrom
ecc-tools/refined-github-projects-1781444461944

Conversation

@ecc-tools

@ecc-tools ecc-tools Bot commented Aug 22, 2026

Copy link
Copy Markdown

Summary

Auto-generated ECC bundle from repository analysis.

What This Does

Merging this PR adds repo-local ECC artifacts for both Claude Code and Codex. The generated bundle captures repository patterns, Codex baseline config, and reusable workflow scaffolds derived from git history analysis.

Analysis Scope

  • Commit history patterns and conventions
  • Code architecture and structure
  • Testing patterns and coverage
  • Recurring workflows

Files

Path Description
.claude/ecc-tools.json ECC install manifest used for upgrades, repair, and uninstall.
.claude/skills/refined-github-projects/SKILL.md Repository-specific Claude Code skill generated from git history.
.agents/skills/refined-github-projects/SKILL.md Codex-facing copy of the generated repository skill.
.agents/skills/refined-github-projects/agents/openai.yaml Codex skill metadata so the repo skill appears cleanly in the skill interface.
.claude/identity.json Suggested identity.json baseline derived from repository conventions.
.codex/config.toml Repo-local Codex MCP and multi-agent baseline aligned with ECC defaults.
.codex/AGENTS.md Codex usage guide that points at the generated repo skill and workflow bundle.
.codex/agents/explorer.toml Read-only explorer role config for Codex multi-agent work.
.codex/agents/reviewer.toml Read-only reviewer role config focused on correctness and security.
.codex/agents/docs-researcher.toml Read-only docs researcher role config for API verification.
.claude/homunculus/instincts/inherited/refined-github-projects-instincts.yaml Continuous-learning instincts derived from repository patterns.
.claude/commands/refactoring.md Workflow command scaffold for refactoring.
Optional: Continuous Learning (12 instincts)

This PR also includes instincts for the continuous-learning-v2 skill. These are optional and only useful if you use that skill.

Import after merging:

/instinct-import .claude/homunculus/instincts/inherited/refined-github-projects-instincts.yaml

Review Checklist

  • Verify detected patterns are accurate
  • Confirm generated config, commands, and skill metadata match the repo’s real workflow
  • Check best practices align with team standards before merging

ECC Tools | Everything Claude Code


Summary by cubic

Introduces an ECC bundle that adds repo-local skills, Codex baseline, and a refactoring workflow to standardize contributions in Claude Code and Codex. No application/runtime code changes; this only adds .claude, .agents, and .codex configuration and documentation.

  • Verify the generated conventions match the repo: conventional commits, vitest with *.test.ts, path aliases, and type-based src/ layout.
  • Review .codex/config.toml defaults: approval_policy = "on-request", sandbox_mode = "workspace-write", web_search = "live", and MCP servers (@modelcontextprotocol/server-github, @upstash/context7-mcp, @playwright/mcp, @modelcontextprotocol/server-memory, @modelcontextprotocol/server-sequential-thinking, Exa).
  • Confirm allow_implicit_invocation: true in .agents/skills/refined-github-projects/agents/openai.yaml is acceptable for your workflows.
  • Note: .claude/ecc-tools.json selects runtime-core and workflow-pack; the security pack is excluded on the free tier.
  • Optional: to enable continuous-learning instincts, run /instinct-import .claude/homunculus/instincts/inherited/refined-github-projects-instincts.yaml.

Written for commit 552d42a. Summary will update on new commits.

Review in cubic

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor auto review

Found 6 actionable issue(s) on changed lines.

The auto-generated ECC bundle adds agent configs and workflow scaffolds, but the repo skill misstates project structure (not a monorepo), documents non-existent module paths and import examples, and omits WXT browser-extension context that root AGENTS.md defines.

Generated automatically when this PR was submitted using Cursor CLI with --model auto.


## Architecture

### Project Structure: Monorepo

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a single-package WXT browser extension, not a monorepo (pnpm-workspace.yaml only holds pnpm settings). Update the structure section so agents don't assume multiple packages.

## Tech Stack

- **Primary Language**: TypeScript
- **Framework**: React

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tech stack omits WXT and the browser-extension model documented in root AGENTS.md. Add WXT, pnpm commands (dev, build, typecheck), and the GraphQL-only architecture so agents use the correct workflow.


### Guidelines

- Group code by type (components, services, utils)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Guidelines reference components/, services/, and utils/, but the repo uses features/, lib/, ui/, entries/, etc. Align folder guidance with the source layout above.


```typescript
// Use path aliases for imports
import { Button } from '@/components/Button'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Example imports use @/components/ and @/hooks/, which don't exist in this repo (sources import from @/lib/ and @/ui/). Replace with paths that match the actual tree.


### Test Framework: vitest

### File Pattern: `*.test.ts`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests also use the *.test.tsx pattern and some live under __tests__/ subfolders. Narrowing to *.test.ts can cause agents to place new tests incorrectly.


## Action

Place code in the appropriate type folder (components/, services/, utils/, etc.)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instinct points agents to components/, services/, and utils/ folders that aren't in this repo; use features/, lib/, and ui/ instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants