Favicon of code-style

code-style Skill

AI Agent SkillPythonOpen source

Guide for running code style linters and formatters. Use this when asked to check code style, run linters, or fix formatting issues. Published by microsoft in semantic-link-labs.

Decision snapshot

Is this a fit?

Best for

Developers using semantic-link-labs, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

2 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is code-style Skill?

Guide for running code style linters and formatters. Use this when asked to check code style, run linters, or fix formatting issues. Published by microsoft in semantic-link-labs. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
68/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Developers using semantic-link-labs

Declared skill metadata

  • Source file: .claude/skills/code-style/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use code-style Skill

  • Use it for developers using semantic-link-labs.

Built with

PythonCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/semantic-link-labs
  • Skill file: .claude/skills/code-style/SKILL.md

What it does

Guide for running code style linters and formatters. Use this when asked to check code style, run linters, or fix formatting issues.

Skill instructions

Code Style and Linting This skill covers code style checking and formatting workflows for the Semantic Link Labs project. When to Use This Skill Use this skill when you need to: - Check code for style violations - Format code with black - Verify type correctness with mypy - Fix linting errors before committing - Ensure code follows project standards --- Formatting Tools | Tool | Purpose | Configuration | |------|---------|---------------| | black | Code formatting | pyproject.toml | | flake8 | Style checking | pyproject.toml | | mypy | Type checking | pyproject.toml | --- Code Formatting with Black The project uses black for code formatting. Running Black bash Format all source files black src/sempylabs tests Check without modifying (dry run) black --check src/sempylabs tests Show diff of changes black --diff src/sempylabs tests Format specific file black src/sempylabs/workspaces.py Black Configuration From pyproject.toml, max line length is configured via flake8 settings. --- Style Ch

Verified compatibility and discovery

Frequently asked questions

What is code-style?

code-style is a open-source AI agent skill with Copy skill directory. Guide for running code style linters and formatters. Use this when asked to check code style, run linters, or fix formatting issues.

Who is code-style best for?

code-style is best for reusing agent instructions, scripts, and references.

How do I install code-style?

Install or run code-style using Copy skill directory. Check code-style for the latest setup command.

Is code-style actively maintained?

code-style may need a closer maintenance check before production use.

Share:

Stars
545
Forks
183
Last commit
2 months ago
Last verified
Aug 28, 2026
Metadata fetched
Aug 28, 2026
Repository age
2 years
License
MIT

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to code-style