Skip to content
Back to skills

Dev.Shortcuts

ASecurity

Mandatory shortcut trigger and usage guidance. ALWAYS check if shortcut applies before responding to ANY coding or development request.

  • 57 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
development

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill dev.shortcuts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dev.Shortcuts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dev.Shortcuts
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-dev-shortcuts/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-dev-shortcuts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: dev.shortcuts
description: Mandatory shortcut trigger and usage guidance. ALWAYS check if shortcut applies before responding to ANY coding or development request. 
---

## Context
Shortcuts are a small self-contained workflow that can be triggered via the keywords `@shortcut:[shortcut]` or `trigger:[shortcut]` 

## Shortcut Location
Shortcuts can be in the following locations

1. Under [shortcuts under skills directory](~/.codex/skills/dev.shortcuts/references/shortcuts/)
2. Inlined in agent instructions under `## Shortcuts`. Shortcut is header text. Can be followed by a space with argument hints enclosed in `[arg_name]`
Examples
```
## Shortcuts

### Foo [arg1] [arg2]
Invokes a foo with [arg1] and [arg2]
```

## Shortcut Trigger and Usage
Any `@shortcut:[shortcut]` or `trigger:[shortcut]` invokes a shortcut and resolves either to the file with the same name in `./references/shortcuts/[shortcut].md` or inlined in the agent instruction. 

If the user asks to promote a shortcut to a skill, use `@shortcut:promote-shortcut-to-skill.md`.

If a shortcut doesn’t resolve, quickly scan the most relevant skill for similarly-named shortcuts before doing broader repo-wide searches.

## Shortcut Chaining
This involves using multiple shortcuts in sequence. Shortcut chaining is denoted by [shortcut1] -> [shortcut2]

Example:
`@shortcut:precommit-process.md -> @shortcut:create-pr.md`

## Mandatory Check Protocol

1. Scan shortcuts in the `./shortcuts` folder. 
2. If a shortcut matches -> Announce: "Using [shortcut name]"
3. Follow the shortcut exactly

## This is NOT Optional

If a shortcut exists for your task, you must use it.
Do not rationalize skipping it.
Common rationalizations to avoid:

- "This is simple, I don't need a shortcut" -> WRONG. Use the shortcut.
- "I know how to do this" -> WRONG. The shortcut may have steps you'll forget.
- "The user didn't ask for a shortcut" -> WRONG. Shortcuts are mandatory when applicable.
- "The shortcut is overkill" -> WRONG. Shortcuts ensure consistency and quality.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.