Agent skill · Code Review & Quality

claude-skill

Use when user asks to leverage claude or claude code to do something (e.g. implement a feature design or review codes, etc). Provides non-interactive automation mode for hands-off task execution without approval prompts.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill claude-skill-fancu1-dotfile --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/agent/claude-skill-fancu1-dotfile/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Claude Code Headless Mode You are operating in **Claude Code headless mode** - a non-interactive automation mode for hands-off task execution. ## Prerequisites Before using this skill, ensure Claude Code CLI is installed and configured: 1. **Installation verification**: ```bash claude --version ``` 2. **First-time setup**: If not installed, guide the user to install Claude Code CLI with command `npm install -g @anthropic-ai/claude-code`. ## References - For extended usage scenarios, see `references/examples.md`. ## Core Principles ### Autonomous Execution - Execute tasks from start to finish without seeking approval for each action - Make confident decisions based on best practices and task requirements - Only ask questions if critical information is genuinely missing - Prioritize completing the workflow over explaining every step ### Output Behavior - Stream progress updates as you work - Provide a clear, structured final summary upon completion - Focus on actionable results and metrics over lengthy explanations - Report what was done, not what could have been done ### Permission Modes Claude Code uses permission modes to control what operations are permitted. Set via `--permiss

What's inside
Steps it walks through
  1. Prerequisites
  2. References
  3. Core Principles
  4. Autonomous Execution
  5. Output Behavior
  6. Permission Modes
  7. Claude Code CLI Commands
  8. Basic Headless Execution
  9. Tool Permissions
  10. Using Permission Modes
  11. Output Formats
  12. Multi-Turn Conversations
  13. System Prompt Customization
  14. MCP Server Configuration
Ships with 1 file
  • metadata.json
Commands it runs
claude --version
claude -p "analyze the codebase structure and explain the architecture"
Allow specific tools
claude -p "stage my changes and write commits" \
Allow multiple tools (space-separated)
claude -p "implement the feature" \
Allow tools with restrictions (comma-separated string)
claude -p "run tests" \
Disallow specific tools
claude -p "analyze the code" \
More from claude-skill-registry
All skills →
About this skill
What does the claude-skill skill do?

Use when user asks to leverage claude or claude code to do something (e.g. implement a feature design or review codes, etc). Provides non-interactive automation mode for hands-off task execution without approval prompts.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill claude-skill-fancu1-dotfile --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going