affaan-m/ecc

terminal-ops

Evidence-first repo execution workflow for ECC.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/affaan-m/ecc --skill terminal-ops

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Terminal Ops

Use this when the user wants real repo execution: run commands, inspect git state, debug CI or builds, make a narrow fix, and report exactly what changed and what was verified.

This skill is intentionally narrower than general coding guidance. It is an operator workflow for evidence-first terminal execution.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • verification-loop for exact proving steps after changes
  • tdd-workflow when the right fix needs regression coverage
  • security-review when secrets, auth, or external inputs are involved
  • github-ops when the task depends on CI runs, PR state, or release status
  • knowledge-ops when the verified outcome needs to be captured into durable project context

When to Use

  • user says "fix", "debug", "run this", "check the repo", or "push it"
  • the task depends on command output, git state, test results, or a verified local fix
  • the answer must distinguish changed locally, verified locally, committed, and pushed

Guardrails

  • inspect before editing
  • stay read-only if the user asked for audit/review only
  • prefer repo-local scripts and helpers over improvised ad hoc wrappers
  • do not claim fixed until the proving command was rerun
  • do not claim pushed unless the branch actually moved upstream

Workflow

1. Resolve the working surface

Settle:

  • exact repo path
  • branch
  • local diff state
  • requested mode:
  • inspect
  • fix
  • verify
  • push

2. Read the failing surface first

Before changing anything:

  • inspect the error
  • inspect the file or test
  • inspect git state
  • use any already-supplied logs or context before re-reading blindly

3. Keep the fix narrow

Solve one dominant failure at a time:

  • use the smallest useful proving command first
  • only escalate to a bigger build/test pass after the local failure is addressed
  • if a command keeps failing with the same signature, stop broad retries and narrow scope

4. Report exact execution state

Use exact status words:

  • inspected
  • changed locally
  • verified locally
  • committed
  • pushed
  • blocked

Output Format

text
SURFACE
- repo
- branch
- requested mode

EVIDENCE
- failing command / diff / test

ACTION
- what changed

STATUS
- inspected / changed locally / verified locally / committed / pushed / blocked

Pitfalls

  • do not work from stale memory when the live repo state can be read
  • do not widen a narrow fix into repo-wide churn
  • do not use destructive git commands
  • do not ignore unrelated local work

Verification

  • the response names the proving command or test
  • git-related work names the repo path and branch
  • any push claim includes the target branch and exact result

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
affaan-m
コミュニティ

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24時間の導入数
489
GitHub Stars
30.8万
更新日
11月20日
affaan-m
コミュニティ

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1時間の導入数
5
GitHub Stars
30.8万
更新日
11月20日
affaan-m
コミュニティ

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1時間の導入数
2
GitHub Stars
30.8万
更新日
11月20日
affaan-m
コミュニティ

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1時間の導入数
2
GitHub Stars
30.8万
更新日
11月20日