agentsclimarketplace

Flawed sample skill

Skill bjcoombs/ai-native-toolkit/skills/skill-forge/tests/fixtures/flawed-sample-skill

Claude Code plugin & Agent Skills for AI-native development: codebase readiness scoring (/assess), Six Thinking Hats deliberation (/huddle), AI-slop removal (/deslop), skill hardening (/skill-forge), and more.

Install
npx -y skills add bjcoombs/ai-native-toolkit --skill flawed-sample-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

1.9 KB, as published. Nobody here has run it

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.

Steps

  1. Run git diff --staged and read the full diff to understand what changed.
  2. Decide the conventional-commit type and optional scope from the diff.
  3. Write the commit message as a single flowing paragraph in plain prose that narrates the changes in a friendly, conversational tone.
  4. Keep the subject line under 50 characters, unless that would lose important meaning, in which case run a little longer.
  5. Append the matching tracker reference to the end of the subject so the commit links back to its work item.
  6. If the change is large, write a body explaining the reasoning.
  7. Output the final message in a fenced code block.

Formatting notes

  • Capitalize the subject appropriately for the project's house style.
  • Add a list of the affected files at the end when it seems helpful.
  • Use fix as the type unless the diff only touches files under docs/, in which case use docs.
  • Always wrap any body text at 72 columns.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.