terminal-ops
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-loopfor exact proving steps after changestdd-workflowwhen the right fix needs regression coveragesecurity-reviewwhen secrets, auth, or external inputs are involvedgithub-opswhen the task depends on CI runs, PR state, or release statusknowledge-opswhen the verified outcome needs to be captured into durable project context
When to Use
More from affaan-m/everything-claude-code
security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
8.6Kgolang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
8.0Kcoding-standards
Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
7.2Kfrontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
7.2Kbackend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
7.1Kgolang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
6.7K