Skip to content
cccskills
FreePublished on GitHub

tiny-fix

Low-ceremony workflow for trivial, low-risk changes: typos, comments, CSS/styling tweaks, string changes, single-line fixes with no logic impact. Use to avoid the overhead of the full feature workflow when the change cannot break anything. If during the fix the change turns out to touch logic, security, config, or schema, stop and escalate to the feature-workflow skill.

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

See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Tiny Fix

Not every change needs the full phased workflow. Applying heavyweight process to a typo wastes time and tokens. This skill is the deliberately minimal path — with a tripwire for when a "tiny" fix turns out not to be.

Qualifies as tiny

  • Typos in strings, comments, or documentation
  • CSS/SCSS styling tweaks with no template logic changes
  • Renaming a label, adjusting copy text
  • A single-line change with no branching-logic impact

Does NOT qualify (escalate to feature-workflow)

  • Anything touching routing, permissions, forms, or user input handling
  • Config entity changes (they need export + review)
  • Schema or entity changes (they need update hooks)
  • Changes to conditionals, loops, or return values
  • "While I'm here" refactors — those are features, not fixes

Procedure

  1. Confirm the change qualifies as tiny (list above). If not — or if you only discover mid-edit that it doesn't — stop and switch to the feature-workflow skill.
  2. Make the change. Nothing else: no drive-by refactoring, no formatting sweeps across the file.
  3. Sanity check: drush cr if templates/CSS aggregation are involved; reload the affected page.
  4. Commit with a one-line message. Done.

Hard rule

The escalation tripwire is the whole point of this skill. A tiny fix that grew is not a tiny fix — never finish a change under this skill that no longer meets the qualification list.

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

Safe deployment workflow for Drupal 10/11 sites: pre-flight checks, backup, the correct update sequence (composer install, database updates, config import, cache rebuild), verification, and rollback plan. Use when deploying to any environment, releasing to production, or when the user asks to "push changes live", "update the server", or run a release. Also use for multisite releases where each site needs its own database update pass.

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

siva01c/claude-plugins16Updated Sep 26, 2026

Use this skill when authoring or editing Docker Compose files (compose.yaml / docker-compose.yml), running multi-container stacks, or containerizing a Drupal/PHP application — e.g. "set up a local Drupal stack with nginx and MariaDB", "add Redis to my compose file", "why won't my containers start", "split dev and prod compose configuration". Also trigger for compose commands (up, down, logs, exec, watch) and healthcheck/dependency issues between services.

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

siva01c/claude-plugins16Updated Sep 26, 2026

Use this skill when running local AI models with Docker Model Runner — the `docker model` CLI — e.g. "run an LLM locally with Docker", "pull a model from the ai/ namespace", "connect my app to a local model", "use a local model as backend for the Drupal AI module", or when wiring the `models:` top-level element into a compose.yaml. Covers pulling/running models, OpenAI-compatible endpoints, and Compose integration.

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

siva01c/claude-plugins16Updated Sep 26, 2026

Use for operational Drupal 11 workflows in DDEV environments, including safe updates, backup-first procedures, and troubleshooting commands.

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

siva01c/claude-plugins16Updated Sep 26, 2026

Use when creating or extending Drupal 11 custom modules, including scaffolding, service architecture, and dependency injection best practices.

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

siva01c/claude-plugins16Updated Sep 26, 2026

Use when auditing Drupal 11 custom modules/themes for security issues such as unsafe input handling, XSS risks, SQL injection, and access control gaps.

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

siva01c/claude-plugins16Updated Sep 26, 2026

See all skills by siva01c

Report a problem with this skill