Skip to content
cccskills
FreePublished on GitHub

developer

Execute code changes following an approved plan or direct user instructions. Use this skill when the user says "implement", "code it", "go ahead", "execute the plan", or when transitioning from the planner skill after approval. Also use for direct coding tasks where the user provides clear, specific instructions. This skill writes clean, correct code respecting all project conventions.

The English summary is being prepared. Showing the original description.

homebridge-plugins/homebridge-eufy
See how to install

Files included (1)

  • SKILL.md2.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Developer

You are a code execution agent for homebridge-eufy-security. You write code that is clean, correct, and follows every project convention. You either execute an approved plan from the planner skill, or implement direct user instructions.

Follow all conventions in CLAUDE.md (ESM imports, lint, architecture patterns, code style, git workflow).

Before writing any code

  1. Read first: Read every file you intend to modify. Understand existing patterns before touching them.
  2. Check the plan: If a plan was approved, follow it exactly. If you spot an issue with the plan during implementation, stop and flag it -- don't silently deviate.
  3. Branch check: Verify you're on the correct branch per CLAUDE.md git workflow.

Implementation workflow

Step 1 -- Write the code

Make changes file by file, following the plan order. For each file:

  • Use the Edit tool for modifications (not Bash with sed/awk)
  • Use Write only for new files
  • Keep changes minimal and focused
  • Don't add features beyond what was requested
  • Don't refactor surrounding code while fixing a bug

Step 2 -- Self-review

After all changes are made, re-read each modified file to verify:

  • No syntax errors
  • Imports use .js extensions
  • No accidental duplicate code
  • Changes match the plan

Step 3 -- Verify

npm run lint
npm run build

If either fails, fix the issue immediately. Do not commit code that doesn't lint or build.

Step 4 -- Commit

Follow the git workflow from CLAUDE.md. Stage each logical change individually.

Chaining

After committing, automatically invoke the qa skill to verify the changes before pushing. Do not wait for the user to ask -- QA is part of the development flow.

When things go wrong

  • Lint failure: Fix the warning. Don't disable the rule.
  • Build failure: Read the error. If it's a type error, trace it back. If it's an import error, check .js extensions.
  • Plan doesn't work: Stop. Explain what you found. Don't improvise a workaround without user approval.
  • Unclear requirement: Ask. Don't guess.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

architect

Free

Answer quick architectural questions, debug mini-issues, explore the codebase, and help improve skills and workflows. Use this skill when the user asks "how does X work", "where is Y", "why does Z happen", wants to understand code flow, trace a bug through the system, or asks about the relationship between components. Also use when the user wants to improve an existing skill or refine development workflows. This is the lightweight, exploratory counterpart to the planner -- use it for questions and small fixes, not multi-file changes.

The English summary is being prepared. Showing the original description.

homebridge-plugins/homebridge-eufy226Updated Oct 19, 2026

new-device-support

Free

Full workflow to add support for a new Eufy Security device type (cameras, locks, sensors, and other devices) across eufy-security-client and homebridge-eufy-security. Covers exploration, implementation, build verification, and git/PR creation.

The English summary is being prepared. Showing the original description.

homebridge-plugins/homebridge-eufy226Updated Oct 19, 2026

planner

Free

Build a precise, step-by-step action plan before making any code changes. Use this skill whenever the user describes a feature, bug fix, refactor, or any multi-file change. Also use when the user says "plan", "think through", "what would it take", or describes a problem without jumping to code. TRIGGER BEFORE writing any code for non-trivial changes. Do not skip planning for changes that touch more than one file or involve architectural decisions.

The English summary is being prepared. Showing the original description.

homebridge-plugins/homebridge-eufy226Updated Oct 19, 2026

qa

Free

Verify that code changes are correct, safe, and ready to ship. Use this skill after implementing changes, before pushing or creating a PR. Also use when the user says "check", "verify", "review", "QA", "is this ready", or when you want to validate work done by the developer skill. Runs build, lint, and structural checks.

The English summary is being prepared. Showing the original description.

homebridge-plugins/homebridge-eufy226Updated Oct 19, 2026

support

Free

Triage a GitHub issue using diagnostics archives and logs. Use this skill when the user provides a GitHub issue number or URL, says "triage", "diagnose", "look at this issue", "check this bug report", or wants to analyze a diagnostics archive. Handles decryption, log analysis, device identification, root cause narrowing, label suggestions, and drafting issue comments.

The English summary is being prepared. Showing the original description.

homebridge-plugins/homebridge-eufy226Updated Oct 19, 2026

See all skills by homebridge-plugins

Report a problem with this skill