--- name: coding-dae963fe694f description: Use when performing coding tasks (implement features, fix bugs, refactor code). Orchestrates language detection, mode switching (normal/autopilot/full-auto), quality enforcement, and verification. allowed-tools: ["shell", "apply_patch", "read_file", "write_file", "update_plan"] metadata: short-description: General coding orchestrator with modes --- # Coding Orchestrator This skill serves as the primary entry point for general coding tasks. It provides: - **Mode switching**: normal (confirm all) / autopilot (confirm risky) / full-auto (minimal confirmation) - **Language detection**: Auto-detect project language and apply appropriate guidance - **Quality enforcement**: Integrate task-discipline, code-quality, verification patterns - **Risk-based confirmation**: Consistent behavior based on operation risk tier **Read these references:** - `references/workflow.md` - Universal coding workflow - `references/quality.md` - Quality priorities (correctness > safety > maintainability) - `references/safety.md` - Runtime + security safety - `references/risk-taxonomy.md` - 4-tier operation risk classification - `references/guardrails.md` - Per-mode guardrails and limits - `~/.config/agent/core/methodology.md` - 5-phase problem-solving - `~/.config/agent/core/task-management.md` - Task discipline patterns --- ## Mode Selection ### Active Mode Determination Mode is determined by (priority order): 1. **Explicit argument**: `mode:autopilot` or `mode:full-auto` prefix in arguments 2. **Session context**: Previously set mode (sticky within session) 3. **Default**: `normal` ### Mode Definitions | Mode | Philosophy | Confirmation Behavior | |------|------------|----------------------| | **normal** | Maximum safety | Confirm for all modifications (Tier 1/2/3) | | **autopilot** | Balanced autonomy | Confirm for risky operations (Tier 1/2), auto for safe (Tier 3/4) | | **full-auto** | Maximum autonomy | Confirm for critical only (Tier 1), auto for all else | See `references/risk-taxonomy.md` for full tier definitions. ### Mode Switching **Explicit mode in arguments:** ``` mode:autopilot fix the bug in handler.go mode:full-auto add tests to all packages ``` **Conversational switching:** User says any of: - "switch to autopilot mode" / "use autopilot" - "switch to full-auto mode" / "go full auto" - "back to normal mode" / "use normal mode" **Mode persistence:** Once set, mode persists for the entire session until explicitly changed. Each new session starts in `normal` mode. **Escalation safeguards:** - normal → autopilot: Acknowledge, proceed - normal → full-auto: Warn about risks, confirm intent, proceed - autopilot → full-auto: Warn about risks, confirm intent, proceed - De-escalation (to more restrictive): Acknowledge, proceed immediately --- ## Language Detection Detect the project's primary language to apply language-specific guidance. ### Detection Priority 1. **Explicit in request**: "fix the Go handler", "update the Python script" 2. **File extension**: `.go`, `.py`, `.rs`, `.ts`, `.js`, `.java`, etc. 3. **Project markers** (check working directory): - `go.mod` → Go - `Cargo.toml` → Rust - `package.json` → JavaScript/TypeScript - `pyproject.toml` or `requirements.txt` → Python - `pom.xml` or `build.gradle` → Java 4. **Ask if ambiguous**: Multiple languages detected or unclear ### Language-Specific Guidance When a language is detected, read and apply ALL guidance from that language's domain: **Go (detected):** ```markdown Read and apply: - `~/.config/agent/domain/coding/go/style.md` - `~/.config/agent/domain/coding/go/idioms.md` - `~/.config/agent/domain/coding/go/concurrency.md` - `~/.config/agent/domain/coding/go/testing.md` - `~/.config/agent/domain/coding/go/tooling.md` - `~/.config/agent/domain/coding/go/organization.md` - `~/.config/agent/domain/coding/go/performance.md` ``` **Python (future):** ```markdown Read and apply: - `~/.config/agent/domain/coding/python/style.md` - `~/.config/agent/domain/coding/python/idioms.md` - (etc.) ``` **Other languages:** Apply generic workflow from `references/workflow.md` and `references/quality.md`. --- ## Workflow The coding skill follows a 5-phase workflow with mode-specific confirmation behavior. ### Phase 1: Context Gathering **Objectives:** - Determine active mode - Detect project language - Read relevant files before modifying - Load language-specific guidance **Steps:** 1. Parse arguments for mode prefix (`mode:autopilot`, `mode:full-auto`) 2. If no explicit mode, check session context for previously set mode 3. If no session mode, use `normal` as default 4. Detect language using priority algorithm 5. Read target files (never modify before reading) 6. Load language-specific guidance modules **Mode behavior:** All modes identical (read-only phase). ### Phase 2: Planning (if non-trivial) **When to plan:** - Tasks requiring 3+ distinct steps - Multi-file modifications - Complex logic changes - Non-obvious implementation approach **Apply task-discipline patterns:** 1. Create TODO list with atomic, testable tasks 2. Use imperative form for content: "Fix bug in parser" 3. Use present continuous for activeForm: "Fixing bug in parser" 4. Ensure exactly ONE task is `in_progress` at any time 5. Mark tasks `completed` immediately after finishing **Mode behavior:** All modes identical (planning phase). ### Phase 3: Implementation Apply universal coding workflow from `references/workflow.md`: 1. **Understand before modifying**: Read code, understand context 2. **Make minimal, targeted changes**: Don't refactor unrelated code 3. **Test incrementally**: Don't save all testing for the end 4. **Document non-obvious decisions**: Add comments where logic isn't self-evident **Mode-specific confirmation behavior:** **Normal mode:** - Propose complete plan upfront - Confirm before EACH file modification - Show exact changes (diff if useful) - Offer options: [P]roceed / [D]iff / [S]kip / [A]bort **Autopilot mode:** - Proceed automatically for Tier 3/4 operations - Report progress: "Created X, Modified Y" - Pause only for Tier 1/2 operations (see `references/risk-taxonomy.md`) - Create checkpoint (git stash) before destructive operations - Track operation count and time limits (see `references/guardrails.md`) - Commits are never auto-run; require explicit confirmation/manual action **Full-auto mode:** - Proceed automatically for Tier 2/3/4 operations (except never-auto overrides) - Audit log all operations with timestamps (see `references/guardrails.md`) - Create checkpoints before major operations (>5 files or git push) - Pause for Tier 1 CRITICAL operations and never-auto overrides (e.g., commits) - Report progress every 10 operations or 5 minutes - Stop after 3 consecutive failures, offer recovery options ### Phase 4: Quality Gates Before claiming completion, enforce quality checks: **Apply code-quality patterns:** 1. **Correctness**: Does the code do what it's supposed to? 2. **Safety**: Any runtime safety issues (nil dereferences, races, leaks)? 3. **Maintainability**: Is the code clear and simple? 4. **Performance**: Any obvious inefficiencies? 5. **Style**: Does it follow language conventions? **Language-specific quality checks:** **Go:** ```bash # Run tests (if applicable) go test -race -count 1 ./... # Run linter (if applicable) golangci-lint run --new=false ./... # Format code golines --base-formatter=gofumpt --ignore-generated --max-len=79 --tab-len=4 --no-reformat-tags --chain-split-dots -w . gofumpt -w . ``` **Mode behavior for quality checks:** - **Normal**: Confirm before running each tool - **Autopilot**: Auto-run tests/lint/format (Tier 3), report results - **Full-auto**: Auto-run all quality checks, only stop if failures block progress ### Phase 5: Verification Apply `verification-before-completion` patterns: **NEVER claim completion without evidence:** 1. Run the verification command (tests, lint, build) 2. Confirm output supports the claim 3. ONLY THEN declare completion **Examples of evidence:** - Tests passing: `ok github.com/user/repo/package 0.123s` - Lint clean: `golangci-lint run` with no output or exit 0 - Build successful: `go build -o /dev/null ./...` with exit 0 - Manual verification: Show output of commands that confirm fix **Mode behavior:** - All modes must provide evidence before completion - Cannot skip verification even in full-auto - If verification fails, apply recovery procedures (see `references/guardrails.md`) --- ## Cross-Skill Coordination ### Absorb (Apply Inline) These skills' patterns are absorbed and applied directly within the coding workflow: | Skill | When | What to Apply | |-------|------|---------------| | `task-discipline` | 3+ step tasks | TODO list with exactly ONE in_progress at any time | | `code-quality` | All coding | Priority order: correctness > safety > maintainability > performance > style | | `verification-before-completion` | Before completion claims | Evidence requirement: run verification, show output, then claim success | ### Delegate (Recommend Invocation) Recommend explicit skill invocation when appropriate: | Condition | Recommended Skill | When to Recommend | |-----------|-------------------|-------------------| | Bugs/test failures encountered | `systematic-debugging` | After 2 failed fix attempts or unclear root cause | | Security-sensitive code | `safety-check` | When modifying auth, crypto, input validation, or data access | | Pre-commit checks needed | `go-precommit` (or language equivalent) | Before creating commits | | Code review requested | `review` | User explicitly asks for review | | Strict TDD requested | `tdd-enforce` | User explicitly requests test-first approach | **Recommendation format:** ``` I encountered test failures. I recommend using the `systematic-debugging` skill for a methodical root-cause analysis. Would you like me to: 1. Continue debugging manually 2. Invoke the systematic-debugging skill 3. Ask you for guidance ``` --- ## Operation Risk Classification Before performing any operation, classify it using the risk taxonomy: **Tier 1 (CRITICAL):** Force push main, credentials, prod DB, external API mutations **Tier 2 (HIGH):** File deletion, git state changes (commit/push/merge/rebase), non-deterministic line edits, package management **Tier 3 (MEDIUM):** New files, tests, deterministic formatting/lint fixes, builds **Tier 4 (LOW):** Read-only operations See `references/risk-taxonomy.md` for complete classification algorithm and examples. **Apply confirmation behavior based on mode and tier:** | Tier | Normal | Autopilot | Full-Auto | |------|--------|-----------|-----------| | 1 | Confirm | Confirm | **Confirm** | | 2 | Confirm | Confirm | Auto | | 3 | Confirm | Auto | Auto | | 4 | Auto | Auto | Auto | **Never-auto overrides** (e.g., `git commit`) supersede this matrix. --- ## Guardrails and Limits Apply limits from `references/guardrails.md` based on active mode: **Autopilot limits:** - Max 10 files modified per operation - Max 100 lines modified per file - Auto-stash before destructive operations **Full-auto limits:** - Report progress every 10 operations or 5 minutes - Pause after 30 minutes - Stop after 3 consecutive failures **Absolute never-auto (all modes including full-auto):** - Git commits (`git commit`, `git commit --amend`) - Force push to main/master - Credential/secret operations - Production deployments - Database migrations on prod --- ## Recovery and Safety ### Checkpoints **Autopilot mode:** ```bash # Before Tier 2 destructive operations git stash push -m "autopilot-checkpoint-$(date +%s)" ``` **Full-auto mode:** ```bash # Before operations affecting >5 files or git push git stash push -m "full-auto-checkpoint-$(date +%s)" ``` ### Rollback on Failure If an operation fails and a checkpoint exists: ``` Operation failed: tests not passing after modification Recovery options: 1. [R]evert to checkpoint 2. [D]ebug the issue 3. [C]ontinue anyway (not recommended) 4. [S]witch to normal mode Choice: _ ``` ### Audit Logging Full-auto mode logs all operations. Autopilot logs Tier 2/3 operations. See `references/guardrails.md` for file location and redaction requirements. Example format: ``` [12:00:01] [FULL-AUTO] [TIER-3] Created: api/handler.go [SUCCESS] [12:00:03] [FULL-AUTO] [TIER-3] Created: api/handler_test.go [SUCCESS] [12:00:05] [FULL-AUTO] [TIER-2] Modified: api/routes.go (+15 lines) [SUCCESS] ``` --- ## Integration with Existing Skills This skill complements (does not replace) existing skills: | Existing Skill | Relationship | |----------------|--------------| | `go-development` | `coding` applies Go guidance when Go detected; users can still invoke `go-development` directly | | `feature` | `coding` handles tactical implementation; `feature` handles strategic 7-phase workflow | | `code-quality` | `coding` absorbs quality patterns inline | | `task-discipline` | `coding` absorbs task patterns for 3+ step work | | `verification-before-completion` | `coding` absorbs verification gate requirement | | `systematic-debugging` | `coding` recommends invocation when bugs encountered | | `safety-check` | `coding` recommends invocation for security-sensitive code | | `review` | `coding` recommends invocation when review requested | --- ## Activation Triggers This skill activates for: - General coding requests: "implement X", "fix bug in Y", "refactor Z" - Mode-prefixed requests: "mode:autopilot add error handling" - Generic file modifications (when not caught by more specific skills) This skill does NOT activate for: - Planning/design requests (use `planner`) - Review requests (use `review`) - Explicit debugging requests (use `systematic-debugging`) - Language-specific tool invocations (use `go-test`, `go-lint`, etc.) --- ## Arguments Mode: ${MODE} Target: ${ARGUMENTS} **Argument patterns:** - `mode:normal implement user authentication` - `mode:autopilot fix all lint errors` - `mode:full-auto add tests for parser package` - `fix bug in handler.go:42` (defaults to normal mode) --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/coding-1/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/coding-1/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, DevOps / SRE, Frontend Developer, Full-Stack Developer, QA / Test Engineer Specialties: API, Backend, Testing Tools: Shell Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: ca701ffe5c381d5e9a1ef0deb254771f26e9dcc6555528ffc98e704356d8031e