Skip to content

aiskillstore/marketplace / skills/0xsero/coder

Write, edit, and refactor code with full tool access - Use when you need to actually write or modify code, create files, run commands, or implement features.

FileKindSize
SKILL.mdskill md852 B
skill-report.jsonconfig8.1 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-04T14:25:09.771Z",
    "slug": "0xsero-coder",
    "source_url": "https://github.com/0xSero/orchestra/tree/main/examples/orchestra/.opencode/skill/coder",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "66517d778c58cbdf1da6e214241e6b1cdf372f313342f911900d5d6809ee3ab2",
    "tree_hash": "7f750aaa747247cb9b297eb406bdb11c127795d5c2ec27089b6569cdbc0b21e2",
    "provenance": {
      "model_effective": "codex",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "coder",
    "description": "Implements focused code changes, creates project files, runs commands, and summarizes tradeoffs for development tasks.",
    "summary": "Implement focused code changes and verify them with project checks when available.",
    "icon": "📦",
    "version": "1.0.1",
    "author": "0xSero",
    "license": "MIT",
    "tags": [
      "coding",
      "implementation",
      "refactoring",
      "testing",
      "developer-productivity"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [],
    "category": "coding"
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "The static network reconnaissance finding is a false positive. SKILL.md describes a general coding assistant for code edits, file creation, command execution, and verification; no prompt injection or malicious intent was found.",
    "remediation": [],
    "risk_factor_evidence": [],
    "static_findings": [
      {
        "id": "blocker:SKILL.md:3:network-reconnaissance",
        "category": "blocker",
        "severity": "low",
        "pattern": "Network reconnaissance",
        "file": "SKILL.md",
        "line_start": 3,
        "line_end": 3,
        "snippet": "description: Write, edit, and refactor code with full tool access - Use when you need to actually wr"
      }
    ],
    "finding_verdicts": [
      {
        "id": "blocker:SKILL.md:3:network-reconnaissance",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "SKILL.md line 3 describes general code editing, file creation, and command execution. No network scanning, host discovery, or reconnaissance intent appears in the reviewed file."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 27,
    "audit_model": "codex",
    "audited_at": "2026-07-04T14:25:09.771Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Implement Focused Code Changes",
    "value_statement": "Turning requirements into safe code changes is time-consuming. This skill edits files, follows project conventions, and verifies behavior with checks when possible.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "AI code editing",
      "code implementation",
      "refactoring assistant",
      "test verification",
      "developer productivity",
      "project conventions",
      "file editing"
    ],
    "actual_capabilities": [
      "Writes and modifies code files for requested changes.",
      "Creates project files needed for features or fixes.",
      "Runs commands to inspect projects and verify behavior.",
      "Refactors code while following existing project conventions.",
      "Summarizes changes, tradeoffs, follow-up work, and risks."
    ],
    "limitations": [
      "Verification depends on tests or checks available in the project.",
      "Large product decisions still need clear user direction.",
      "Generated changes should receive normal human code review.",
      "It cannot guarantee compatibility when dependencies or services are unavailable."
    ],
    "use_cases": [
      {
        "title": "Implement Small Features",
        "description": "Add focused functionality, update related files, and run relevant checks when available.",
        "target_user": "Product engineer"
      },
      {
        "title": "Refactor Existing Code",
        "description": "Improve structure while preserving behavior and matching local style.",
        "target_user": "Code maintainer"
      },
      {
        "title": "Prepare Changes for Review",
        "description": "Collect edits, verification results, tradeoffs, and follow-up risks for reviewers.",
        "target_user": "Technical lead"
      }
    ],
    "prompt_templates": [
      {
        "title": "Make a Small Change",
        "scenario": "Beginner feature request",
        "prompt": "Update the project to support this requirement: [describe requirement]. Keep the change minimal, run relevant checks, and summarize the files touched."
      },
      {
        "title": "Fix a Bug",
        "scenario": "Focused debugging task",
        "prompt": "Investigate why [describe broken behavior]. Identify the root cause, make the smallest reliable fix, and verify it with a focused test or check."
      },
      {
        "title": "Refactor Safely",
        "scenario": "Behavior-preserving improvement",
        "prompt": "Refactor [area or module] to improve [goal]. Preserve existing behavior, follow local patterns, and call out any remaining risk."
      },
      {
        "title": "Implement and Validate Workflow",
        "scenario": "Advanced multi-file implementation",
        "prompt": "Implement [workflow] across the necessary files. Add or update tests, run project checks, and explain the main tradeoffs."
      }
    ],
    "output_examples": [
      {
        "input": "Add validation to the profile update flow.",
        "output": "Updated the profile flow with validation, added user-facing error handling, and ran the relevant form checks."
      },
      {
        "input": "Refactor the settings module to reduce duplication.",
        "output": "Consolidated repeated settings logic, preserved existing behavior, and noted one follow-up cleanup for a related module."
      },
      {
        "input": "Find and fix the failing checkout test.",
        "output": "Identified a missing state update, applied a focused fix, and verified the checkout test passes."
      }
    ],
    "best_practices": [
      "Provide clear acceptance criteria and affected paths when known.",
      "Keep requests focused before asking for broad refactors.",
      "Request the specific checks that matter for your project."
    ],
    "anti_patterns": [
      "Do not ask for broad rewrites without priorities or success criteria.",
      "Do not skip verification when tests or build commands are available.",
      "Do not mix unrelated product, style, and infrastructure changes."
    ],
    "faq": [
      {
        "question": "Does this skill write code directly?",
        "answer": "Yes. It is designed to edit files, create files, and implement requested development changes."
      },
      {
        "question": "Can it run tests or project commands?",
        "answer": "Yes. It can run relevant commands when the environment and project setup allow it."
      },
      {
        "question": "Is it only for new features?",
        "answer": "No. It can also fix bugs, refactor code, and prepare changes for review."
      },
      {
        "question": "Does it replace code review?",
        "answer": "No. Its output should still receive normal review, especially for important systems."
      },
      {
        "question": "What information should I provide?",
        "answer": "Provide the goal, constraints, affected files when known, and expected verification steps."
      },
      {
        "question": "Can it handle large changes?",
        "answer": "It can work across multiple files, but clear scope and staged requests produce better results."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 27
    }
  ]
}
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall