$ loading_
Apply the right commit prefix, reviewer, and test plan for code changes.
The material indicates this skill only provides textual commit/reviewer/test-plan conventions, with no keys, no remote endpoints, and no stated execution or data-access capability. Overall risk is low based on the provided facts, with only minor caution around weak source mapping and unclear maintenance context.
The material explicitly states that no keys or environment variables are required; the README only describes commit title, reviewer, and test plan conventions, with no credential collection, storage, or transmission.
The material lists no remote endpoints, and the content is prompt/documentation-style guidance with no description of sending user data to external services.
The system flags it as prompt-only; the README only provides commit conventions and contains no installation, script execution, local process spawning, or system-call behavior.
No capability to read, write, or modify local files/repository content is declared; based on the material, it only provides textual suggestions from the change area and does not indicate data-access permissions.
A positive factor is that it is marked open-source and hosted on GitHub; however, the repository link points to facebook/pyre-check rather than matching the skill name directly, and the listing shows 0 stars, no declared license, and unknown maintenance status. Source mapping and sustainability signals are weak, so manual verification of provenance is advisable.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "commit-conventions" skill from askskill: 1. Download https://raw.githubusercontent.com/facebook/pyre-check/main/.llms/skills/commit-conventions/SKILL.md 2. Save it as ~/.claude/skills/commit-conventions/SKILL.md 3. Reload skills and tell me it's ready
I changed the form validation logic on the frontend login page and updated the related unit tests. Based on the code area, recommend the correct commit title prefix, reviewer, and test plan, and output a standard commit message.
A commit message with the correct prefix, suggested reviewer, and test plan.
Here is a diff for a backend API change. Identify the relevant code area and add the appropriate title prefix, reviewer, and test plan in a format suitable for code review.
A review-ready diff description with prefix, reviewer, and test plan.
I changed a database migration, service-layer logic, and monitoring configuration. Based on the primary area affected, determine the commit title prefix, reviewer, and test plan, and explain the reasoning.
A commit recommendation categorized by the primary change area, with brief reasoning.
When creating commits:
[pysa] as a prefix in the commit title. Otherwise, add [pyre] as a prefix in the commit title.#pysa_swe as a reviewer. Otherwise, add #pyre as a reviewer.make test in the test plan.Debug Pysa false negatives by comparing outputs and locating lost taint flows.
Read, write, and debug Pysa JSON taint models and .models output.
Run, debug, and update Pysa taint analysis end-to-end integration tests.
Understand the Pyre/Pysa architecture and locate key implementations quickly.
Get idiomatic Relay guidance for React code, debugging, and code reviews.
Write and run Markdown-driven end-to-end tests for Relay apps.
Generate standardized Git commits from diffs with logical grouping support.
Capture the why behind git changes with standardized contextual commit history.
Create commits for code changes with AI-generated messages matching repo style.
Fix lint, formatting, and common code issues before passing CI.
Generate shareable code or text diffs for review and collaboration.
Finalize completed work by committing, pushing, and opening reviewed pull requests.