Skip to content
Back to skills

Consult Guidelines

ASecurity

Review relevant guidelines before starting a task

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
developmentpythongorefactoringgit

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill consult-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Consult Guidelines?

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

Security grade badge for Consult Guidelines
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-consult-guidelines/badge)](https://www.skillsdirectory.com/skills/majiayu000-consult-guidelines)

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: consult-guidelines
description: Review relevant guidelines before starting a task
---

## Overview

Read and internalize the coding guidelines relevant to the current task. This ensures consistent application of standards across all work.

## Parameters

- **task_type** (optional): "python", "git", "refactor", "debug", "review", or "all"

## Steps

### 1. Determine Relevant Guidelines

Based on task type, identify which guidelines to review.

**Mapping:**
- `python` → coding-standards.md, python-standards.md
- `git` → git-workflow.md
- `refactor` → coding-standards.md, anti-patterns.md
- `debug` → coding-standards.md (TDD section)
- `review` → anti-patterns.md, coding-standards.md
- `all` → all guidelines

**Constraints:**
- You MUST read `guidelines/coding-standards.md` for any code changes
- You MUST read `guidelines/python-standards.md` for Python work
- You MUST read `guidelines/git-workflow.md` before any commits
- You SHOULD read `guidelines/anti-patterns.md` before code review or refactoring

### 2. Summarize Key Points

Extract the 3-5 most relevant rules for the current task.

**Constraints:**
- You MUST highlight any MUST/MUST NOT constraints
- You SHOULD note any task-specific gotchas

### 3. Apply During Work

Keep these guidelines in mind while executing the task. Reference them when making decisions.

**Constraints:**
- You MUST cite the relevant guideline when it influences a decision
- You SHOULD flag if you discover a case not covered by guidelines

## Examples

**User:** "I'm about to refactor the auth module"
**Agent:** Reads coding-standards.md and anti-patterns.md, summarizes DRY principles and slop patterns to avoid, proceeds with refactor while citing guidelines.

**User:** "/consult-guidelines python"
**Agent:** Reviews coding-standards.md and python-standards.md, extracts key rules about ruff, type hints, and path management.

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.