Skip to content

feat: add agent-skills ECC bundle#2

Open
ecc-tools[bot] wants to merge 11 commits into
mainfrom
ecc-tools/agent-skills-1777163923073
Open

feat: add agent-skills ECC bundle#2
ecc-tools[bot] wants to merge 11 commits into
mainfrom
ecc-tools/agent-skills-1777163923073

Conversation

@ecc-tools

@ecc-tools ecc-tools Bot commented Apr 26, 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/agent-skills/SKILL.md Repository-specific Claude Code skill generated from git history.
.agents/skills/agent-skills/SKILL.md Codex-facing copy of the generated repository skill.
.agents/skills/agent-skills/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/agent-skills-instincts.yaml Continuous-learning instincts derived from repository patterns.
Optional: Continuous Learning (14 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/agent-skills-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 Sourcery

Add repository-specific ECC configuration and skills for Claude and Codex, including multi-agent setups and learned development patterns.

New Features:

  • Introduce Claude and Codex repo skills documenting agent-skills development conventions and workflows.
  • Provide Codex baseline configuration with MCP servers and multi-agent agent profiles for exploration, review, and docs research.

Enhancements:

  • Add continuous-learning instincts capturing repository coding, testing, and commit conventions.
  • Document Codex ECC usage and available agents in a repo-local AGENTS guide.
  • Register the agent-skills repo skill with Codex via OpenAI agent metadata and supporting Claude identity/manifest files.

Documentation:

  • Add markdown skill guides describing coding standards, testing patterns, and common workflows for the agent-skills repository.

Summary by cubic

Adds a repo-local ECC bundle for Claude Code and Codex, including a generated repo skill, Codex baseline with multi-agent roles, and a suggested identity.json. This makes repo patterns and workflows available in-tool and standardizes local agent setup.

  • New Features

    • Repo skill for Claude Code at .claude/skills/agent-skills/SKILL.md and Codex copy at .agents/skills/agent-skills/SKILL.md with UI metadata at .agents/skills/agent-skills/agents/openai.yaml.
    • Codex baseline at .codex/config.toml enabling MCP servers: @modelcontextprotocol/server-github, @upstash/context7-mcp, Exa, @modelcontextprotocol/server-memory, @playwright/mcp, @modelcontextprotocol/server-sequential-thinking.
    • Multi-agent configs: explorer, reviewer, and docs-researcher in .codex/agents/*.
    • Suggested .claude/identity.json aligned to repo conventions.
    • Optional continuous-learning instincts at .claude/homunculus/instincts/inherited/agent-skills-instincts.yaml.
  • Migration

    • Optional: import instincts with /instinct-import .claude/homunculus/instincts/inherited/agent-skills-instincts.yaml.
    • Verify the generated patterns and commands match your team’s workflow before relying on them.

Written for commit 7a725d8. Summary will update on new commits.

@sourcery-ai

sourcery-ai Bot commented Apr 26, 2026

Copy link
Copy Markdown

Reviewer's Guide

Adds an auto-generated ECC bundle for the agent-skills repo, including Claude and Codex skills, Codex multi-agent configuration, and continuous-learning instincts derived from repository analysis.

Sequence diagram for Codex reviewer agent using repo skill and MCP

sequenceDiagram
  actor Developer
  participant CodexCLI
  participant Config as Codex_config.toml
  participant Reviewer as Reviewer_agent
  participant RepoSkill as Repo_skill_agent_skills
  participant GithubMCP as MCP_github

  Developer->>CodexCLI: Invoke reviewer agent
  CodexCLI->>Config: Load multi_agent configuration
  Config-->>CodexCLI: Agent and MCP settings
  CodexCLI->>Reviewer: Start session with sandbox_mode read-only
  Reviewer->>RepoSkill: Apply repo patterns and workflows
  RepoSkill-->>Reviewer: Conventions and commands
  Reviewer->>GithubMCP: Fetch PR diff and repository context
  GithubMCP-->>Reviewer: PR files, commits, metadata
  Reviewer-->>Developer: Review focused on correctness, security, tests
Loading

File-Level Changes

Change Details Files
Introduce continuous-learning instincts capturing repo-specific coding, testing, and git conventions.
  • Add multiple instincts with triggers, confidence scores, and domains for commit formatting, naming conventions, imports/exports, test locations, and skills folder usage.
  • Document evidence for each instinct based on repository analysis to guide future automated behavior.
.claude/homunculus/instincts/inherited/agent-skills-instincts.yaml
Add mirrored Claude and Codex skills describing agent-skills development patterns and workflows.
  • Define repository-specific development patterns for file naming, import/export style, commit message patterns, and testing approach.
  • Document common workflows and task commands for adding/refactoring skills and running tests.
  • Provide identical skill content for both Claude and Codex so each platform exposes the same repo guidance.
.agents/skills/agent-skills/SKILL.md
.claude/skills/agent-skills/SKILL.md
Configure Codex MCP baseline and multi-agent roles for this repo.
  • Set Codex config defaults including approval policy, sandbox mode, web search, and enabled MCP servers.
  • Enable multi-agent support with global limits and define explorer, reviewer, and docs_researcher agents wired to per-role config files.
  • Document how these agents and the repo skill should be used in the Codex CLI via AGENTS.md.
.codex/config.toml
.codex/AGENTS.md
.codex/agents/explorer.toml
.codex/agents/reviewer.toml
.codex/agents/docs-researcher.toml
Expose the repo skill cleanly in the Codex/OpenAI skill interface.
  • Define user-facing metadata for the agent-skills Codex skill, including display name, description, default prompt, and implicit invocation policy.
.agents/skills/agent-skills/agents/openai.yaml
Add ECC tooling manifest and identity baseline for Claude (content not shown in diff).
  • Introduce ecc-tools manifest used for ECC install/upgrade/repair flows for this repo.
  • Add a suggested Claude identity baseline aligned with detected repository conventions.
.claude/ecc-tools.json
.claude/identity.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai 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.

Hey - I've found 2 issues, and left some high level feedback:

  • Both SKILL.md files are wrapped in a top-level ```markdown code fence, which will prevent them from rendering as actual markdown in many viewers; consider removing the outer fence so the content is rendered normally.
  • The instincts YAML includes overlapping rules for similar behaviors (e.g., file naming, import/export style, commit messages) with slightly different ids and triggers; it may be worth deduplicating or consolidating these to avoid conflicting guidance at runtime.
  • In agent-skills-instincts.yaml, the trigger and source_repo fields are inconsistently formatted (e.g., capitalized vs lowercase triggers, URL vs org/repo strings); aligning these formats will make the metadata more uniform and easier to process.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Both SKILL.md files are wrapped in a top-level ```markdown code fence, which will prevent them from rendering as actual markdown in many viewers; consider removing the outer fence so the content is rendered normally.
- The instincts YAML includes overlapping rules for similar behaviors (e.g., file naming, import/export style, commit messages) with slightly different ids and triggers; it may be worth deduplicating or consolidating these to avoid conflicting guidance at runtime.
- In `agent-skills-instincts.yaml`, the `trigger` and `source_repo` fields are inconsistently formatted (e.g., capitalized vs lowercase triggers, URL vs `org/repo` strings); aligning these formats will make the metadata more uniform and easier to process.

## Individual Comments

### Comment 1
<location path=".codex/config.toml" line_range="6" />
<code_context>
+# ECC Tools generated Codex baseline
+approval_policy = "on-request"
+sandbox_mode = "workspace-write"
+web_search = "live"
+
+[mcp_servers.github]
</code_context>
<issue_to_address>
**🚨 question (security):** Reconfirm that `web_search = "live"` is appropriate from a security/privacy standpoint for this project.

Because live web search increases the risk of data exfiltration and unpredictable external inputs, please confirm this repo will not handle sensitive or proprietary code, or add guardrails (e.g., limiting when/where web search is enabled) to align with your security posture.
</issue_to_address>

### Comment 2
<location path=".codex/config.toml" line_range="16" />
<code_context>
+command = "npx"
+args = ["-y", "@upstash/context7-mcp@latest"]
+
+[mcp_servers.exa]
+url = "https://mcp.exa.ai/mcp"
+
</code_context>
<issue_to_address>
**question (bug_risk):** Validate that the `mcp_servers.exa` configuration using only a `url` matches the expected MCP server schema.

`exa` is configured only with a `url`, whereas the others use `command`/`args`. If the MCP runtime expects the same shape for all entries or special handling for HTTP servers, this could cause runtime issues or the server being ignored. Please confirm this format against the current `config-schema.json` and the Exa MCP docs.
</issue_to_address>

Fix all in Cursor


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread .codex/config.toml
# ECC Tools generated Codex baseline
approval_policy = "on-request"
sandbox_mode = "workspace-write"
web_search = "live"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🚨 question (security): Reconfirm that web_search = "live" is appropriate from a security/privacy standpoint for this project.

Because live web search increases the risk of data exfiltration and unpredictable external inputs, please confirm this repo will not handle sensitive or proprietary code, or add guardrails (e.g., limiting when/where web search is enabled) to align with your security posture.

Fix in Cursor

Comment thread .codex/config.toml
command = "npx"
args = ["-y", "@upstash/context7-mcp@latest"]

[mcp_servers.exa]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

question (bug_risk): Validate that the mcp_servers.exa configuration using only a url matches the expected MCP server schema.

exa is configured only with a url, whereas the others use command/args. If the MCP runtime expects the same shape for all entries or special handling for HTTP servers, this could cause runtime issues or the server being ignored. Please confirm this format against the current config-schema.json and the Exa MCP docs.

Fix in Cursor

@cubic-dev-ai cubic-dev-ai 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.

4 issues found across 11 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".agents/skills/agent-skills/SKILL.md">

<violation number="1" location=".agents/skills/agent-skills/SKILL.md:1">
P2: Remove the outer Markdown code fences so the document renders as Markdown instead of a single code block.</violation>
</file>

<file name=".codex/AGENTS.md">

<violation number="1" location=".codex/AGENTS.md:26">
P3: This sentence references workflow files that do not exist, which contradicts the previous line and can mislead users.</violation>
</file>

<file name=".codex/config.toml">

<violation number="1" location=".codex/config.toml:14">
P2: Pin MCP package versions in the baseline config instead of using floating `@latest`/unversioned `npx` installs.</violation>
</file>

<file name=".claude/skills/agent-skills/SKILL.md">

<violation number="1" location=".claude/skills/agent-skills/SKILL.md:1">
P2: The file is wrapped in a fenced code block, so the entire SKILL.md renders as literal code instead of documentation.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

@@ -0,0 +1,88 @@
```markdown

@cubic-dev-ai cubic-dev-ai Bot Apr 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2: Remove the outer Markdown code fences so the document renders as Markdown instead of a single code block.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .agents/skills/agent-skills/SKILL.md, line 1:

<comment>Remove the outer Markdown code fences so the document renders as Markdown instead of a single code block.</comment>

<file context>
@@ -0,0 +1,88 @@
+```markdown
+# agent-skills Development Patterns
+
</file context>
Fix with Cubic

Comment thread .codex/config.toml

[mcp_servers.context7]
command = "npx"
args = ["-y", "@upstash/context7-mcp@latest"]

@cubic-dev-ai cubic-dev-ai Bot Apr 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2: Pin MCP package versions in the baseline config instead of using floating @latest/unversioned npx installs.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .codex/config.toml, line 14:

<comment>Pin MCP package versions in the baseline config instead of using floating `@latest`/unversioned `npx` installs.</comment>

<file context>
@@ -0,0 +1,48 @@
+
+[mcp_servers.context7]
+command = "npx"
+args = ["-y", "@upstash/context7-mcp@latest"]
+
+[mcp_servers.exa]
</file context>
Fix with Cubic

@@ -0,0 +1,88 @@
```markdown

@cubic-dev-ai cubic-dev-ai Bot Apr 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2: The file is wrapped in a fenced code block, so the entire SKILL.md renders as literal code instead of documentation.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .claude/skills/agent-skills/SKILL.md, line 1:

<comment>The file is wrapped in a fenced code block, so the entire SKILL.md renders as literal code instead of documentation.</comment>

<file context>
@@ -0,0 +1,88 @@
+```markdown
+# agent-skills Development Patterns
+
</file context>
Fix with Cubic

Comment thread .codex/AGENTS.md

- No dedicated workflow command files were generated for this repo.

Use these workflow files as reusable task scaffolds when the detected repository workflows recur. No newline at end of file

@cubic-dev-ai cubic-dev-ai Bot Apr 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P3: This sentence references workflow files that do not exist, which contradicts the previous line and can mislead users.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .codex/AGENTS.md, line 26:

<comment>This sentence references workflow files that do not exist, which contradicts the previous line and can mislead users.</comment>

<file context>
@@ -0,0 +1,26 @@
+
+- No dedicated workflow command files were generated for this repo.
+
+Use these workflow files as reusable task scaffolds when the detected repository workflows recur.
\ No newline at end of file
</file context>
Fix with Cubic

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