phx-quick
/phx-quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
- Author
- oliver-kriska ↗
- Repository
- claude-elixir-phoenix ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
Original author description
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
How it works
- Usage
- Arguments
- How It Differs
- Workflow
- Iron Laws
- Rules in Quick Mode
- When to Use
- Quick Patterns
- Escape Hatch
- Verification
SKILL.md preview
---
name: phx-quick
description: Implement small Phoenix changes without planning — add validations, update
routes, fix components, create migrations. Use for single-file edits under 50 lines.
---
# Quick Mode
Skip the planning ceremony. Get working code fast.
## Usage
```bash
/phx-quick Add pagination to posts
/phx-quick Fix the login redirect bug
/phx-quick Add CSV export to reports
```
## Arguments
`$ARGUMENTS` = What to implement
## How It Differs
| Normal Mode | Quick Mode |
|-------------|------------|
| Spawn research agents | No agents |
| Create plan document | Mental model only |
| Parallel review | Optional single review |
| Multiple iterations | Single pass |
## Workflow
1. **Understand** - Read the files the change touches
2. **Implement** - Write code directly
3. **Verify** - Quick compile check
4. **Done** - No ceremony
## Iron Laws
1. **NEVER skip verification** — run `mix compile --warnings-as-errors` after every change, even in quick mode
2. **DO NOT touch files outside the stated scope** — quick mode means minimal blast radius; if a fix requires changes across multiple domains, escalate to `/phx-plan`
3. **NEVER bypass security checks for speed** — auth, input validation, and XSS rules apply regardless of change size
## Rules in Quick Mode
### Still Enforced (Iron Laws)
- ✓ No process without runtime reason
- ✓ No DB in mount
- ✓ Security basics (no SQL injection, etc.)
- ✓ Run `mix format`
### Skipped
- ✗ Parallel agent research
- ✗ Written plan document
- ✗ Multiple review passes
- ✗ Documentation updates
## When to Use
**Good for:**
- Bug fixes with clear solution
- Small features (<100 lines)
- Refactoring with tests
- Adding fields/columns
- UI tweaks
**Not for:**
- New authentication flows
- Payment integration
- Data migrations
- Architectural changes
- Anything touching security
## Quick Patterns
### Add Field
```bash
/quick Add phone field to users
```
→ Migration + schema + changeset + form field
### Fix Bug
```bash
/quick Fix: posts not showing for admin users
```
→ Find issue + fix + verify
### Add Endpoint
```bash
/quick Add GET /api/health endpoint
```
→ Route + controller + response
## Escape Hatch
If quick mode hits complexity:
```
This needs more planning. Switching to normal mode.
Run /phx-plan [task] for full analysis.
```
## Verification
After quick implementation:
Run `mix compile --warnings-as-errors`. If you touched Ecto schemas or migrations,
run `mix ecto.migrate`. Then run `mix test test/path_test.exs` for affected tests.
## Example Session
```
User: /phx-quick Add archived_at timestamp to posts
Claude:
1. Reading lib/my_app/blog/post.ex...
2. Creating migration...
# priv/repo/migrations/xxx_add_archived_at_to_posts.exs
def change do
alter table(:posts) do
add :archived_at, :utc_datetime
end
end
3. Updating schema...
# lib/my_app/blog/post.ex
field :archived_at, :utc_datetime
4. Adding to changeset...
def changeset(post, attrs) do
post
|> cast(attrs, [:title, :body, :archived_at])
...
end
5. Verifying...
$ mix compile --warnings-as-errors ✓
$ mix ecto.migrate ✓
$ mix test test/my_app/accounts_test.exs ✓
Done.
```
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 9a6840178380 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines. - 100phx-full
Run portable end-to-end lifecycle with gates. Use for full features; use $elixir-phoenix:phx-work for an existing plan. - 100phoenix-auth-customization
Use when adding fields to the phx.gen.auth user — usernames, profile fields, a registration changeset, migrations and fixtures alongside generated auth. Not for on_mount/live_session (phoenix-liveview-auth) or permissions (phoenix-authorization-patterns). - 100gendiff
Use elixirstream.dev's gendiff API to see exactly what changed between two versions (and flag sets) of an Elixir/Phoenix code generator, so you upgrade from real diffs instead of guessing. Trigger this whenever the user wants to upgrade or bump Phoenix, phx.new, phx.gen.auth,… - 100phoenix-liveview-auth
Use when protecting LiveViews with the generated phx.gen.auth code — on_mount hooks, live_session, mount_current_scope, sudo mode, logout disconnects, auth tests. Not for extra user fields (phoenix-auth-customization) or per-record permissions (phoenix-authorization-patterns).