Individual skill

flawed-sample-skill

Helps with writing. Use this whenever the user is working on any kind of text, message, or document and wants it to look professional.

skills/skill-forge/tests/fixtures/flawed-sample-skill/SKILL.md

Read pinned source

Source commit 82a6017d2079ff660452106e2f48e3030801feb5

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Instructions only
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 32
Repository last updated: Oct 16, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agentic-ai Repository topic
ai-agents Repository topic
anthropic Repository topic
claude Repository topic
claude-code Repository topic
claude-code-plugin Repository topic
claude-skills Repository topic
code-quality Repository topic
codebase-analysis Repository topic
writing Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

DEFECTS.mddoc · 3,826 bytes
SKILL.mdcore · 1,978 bytes
SKILL.mdcore · 1,978 bytes

Read excerpt


# Commit Message Writer

Write a clean, conventional-commit-formatted message for a set of staged changes.

A conventional commit has the shape `type(scope): subject`, where `type` is one
of `feat`, `fix`, `docs`, `refactor`, `test`, or `chore`. The subject is a short
imperative summary. Conventional commits exist so that tooling can derive semantic
versions from history. Semantic versioning, or semver, is a three-part version
number `MAJOR.MINOR.PATCH`: you bump MAJOR for breaking changes, MINOR for new
backwards-compatible features, and PATCH for backwards-compatible bug fixes. The
versions are ordered, so `1.4.2` is older than `1.4.10`, and a leading `0.y.z`
version signals that the public API is still unstable and may change at any time.
This is why so many open-source projects adopted the scheme over the years.