Skill Introduction

Overview

ECC の現在のエージェント、スキル、コマンド、フック、ルール、インストールプロファイル、およびプロジェクトオンボーディングをガイドしています。ライブリポジトリサーフェスを読んでから回答するようユーザーをガイドします。

Core value

Turns reusable Testing know-how into an installable skill, helping users complete github, community, claude, claude-code work faster.

Target users

Developers, testers, and maintainers who handle Testing tasks in Focus Code.
Teams that already trust workflows or content from affaan-m.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community, claude, claude-code that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Testing, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, claude, claude-code, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install ecc-guide-6bc147

View source

Detail Preview

SKILL.md

Primary filemarkdown6 KB

name: ecc-guide description: ECC の現在のエージェント、スキル、コマンド、フック、ルール、インストールプロファイル、およびプロジェクトオンボーディングをガイドしています。ライブリポジトリサーフェスを読んでから回答するようユーザーをガイドします。 origin: community

ECC Guide

Use this skill when a user needs help understanding, navigating, installing, or choosing parts of Everything Claude Code.

When To Use

Use this skill when the user:

asks what ECC includes
wants help finding a skill, command, agent, hook, rule, or install profile
is new to the repository and needs a guided path
asks "how do I do X with ECC?"
asks which ECC components fit a project
needs a lightweight explanation of how commands, skills, agents, hooks, and rules relate
is confused by install paths, duplicate installs, reset/uninstall, or selective install options

Core Principle

Answer from current files, not memory. ECC changes quickly, so hard-coded catalog counts, feature lists, and install instructions go stale.

When the ECC repository is available, inspect the relevant files before giving a concrete answer:

node scripts/ci/catalog.js --json
find skills -maxdepth 2 -name SKILL.md | sort
find commands -maxdepth 1 -name '*.md' | sort
find agents -maxdepth 1 -name '*.md' | sort
node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --list-components --json

Use the smallest set of reads needed for the user's question.

Repository Map

README.md: install paths, uninstall/reset guidance, public positioning, FAQs
AGENTS.md: contributor guidance and project structure
agent.yaml: exported gitagent surface and command list
commands/: maintained slash-command compatibility shims
skills/*/SKILL.md: reusable workflows and domain playbooks
agents/*.md: delegated subagent role prompts
rules/: language and harness rules
hooks/README.md, hooks/hooks.json, scripts/hooks/: hook behavior and safety gates
manifests/install-*.json: selective install modules, components, profiles, and target support
docs/: harness guides, architecture notes, translated docs, release docs

Response Style

Lead with the answer, then give the next action. Most users do not need a full catalog dump.

Good first response shape:

what to use
why it fits
exact file or command to inspect
one next command or question

Avoid:

listing every skill or command by default
repeating large README sections
recommending retired command shims when a skill-first path exists
claiming a component exists without checking the filesystem
replacing install guidance with manual copy commands when the managed installer supports the target

Common Tasks

New User Onboarding

Give a short menu:

install or reset ECC
pick skills for a project
understand commands vs skills
inspect hooks and safety behavior
run a harness audit
find a specific workflow

Point to README.md for install/reset and /project-init for project-specific onboarding.

Feature Discovery

For "what should I use for X?":

Search skills/, commands/, and agents/.
Prefer skills as the primary workflow surface.
Use commands only when they are a maintained compatibility shim or a user explicitly wants slash-command behavior.
Mention agents when delegation is useful.

Useful searches:

rg -n "<query>" skills commands agents docs
find skills -maxdepth 2 -name SKILL.md | sort

Install Guidance

Use managed install paths:

node scripts/install-plan.js --list-profiles
node scripts/install-plan.js --profile minimal --target claude --json
node scripts/install-apply.js --profile minimal --target claude --dry-run

For specific skill installs:

node scripts/install-plan.js --skills <skill-id> --target claude --json
node scripts/install-apply.js --skills <skill-id> --target claude --dry-run

Warn users not to stack plugin installs and full manual/profile installs unless they intentionally want duplicate surfaces.

Project Onboarding

Use /project-init when the user wants ECC configured for a target repo. The expected sequence is:

detect the stack from project files
resolve a dry-run install plan
inspect existing CLAUDE.md and settings files
ask before applying changes
keep generated guidance minimal and repo-specific

Troubleshooting

Ask for the target harness and install path first, then inspect:

plugin install metadata
.claude/, .cursor/, .codex/, .gemini/, .opencode/, .codebuddy/, .joycode/, or .qwen/
hooks/hooks.json
install-state files
relevant command/skill files

For repo health, suggest:

npm run harness:audit -- --format text
npm run observability:ready
npm test

Output Templates

Short Recommendation

Use <skill-or-command>. It fits because <reason>.

Canonical file: <path>
Verify with: <command>
Next: <one concrete action>

Search Results

Best matches:
- <path>: <why it matters>
- <path>: <why it matters>

Recommendation: <which one to use first and why>

Install Plan Summary

Detected: <stack evidence>
Target: <harness>
Plan: <profile/modules/skills>
Dry run: <command>
Would change: <paths>
Needs approval before apply: <yes/no>

Related Surfaces

/project-init: stack-aware onboarding plan for a target repo
/harness-audit: deterministic readiness scorecard
/skill-health: skill quality review
/skill-create: generate a new skill from local git history
/security-scan: inspect Claude/OpenCode configuration security

ecc guide