| name | friction-log |
| description | File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.
|
Friction log
Read
docs/contributing/friction-log.md.
Do not write entries under .agents/friction-log/ or docs/friction-log/.
This is not a product feature request. Use a normal GitHub issue for those. Use
this skill for developing educlopez/friction-log.
File friction
When you hit a papercut and cannot (or should not) fix it in the current change,
file it before you forget.
Search open issues first:
gh issue list --repo educlopez/friction-log --label friction --state open --limit 200
Comment on a match instead of opening a duplicate.
Title: Friction: <what hurt>.
Label: friction.
Body:
## What happened
What you were doing and what got in the way.
## What you wanted
The expected path.
## How to reproduce
Commands, files, or conditions. Enough for a later agent to investigate without
this session.
## Cost
Time lost, how often this happens, who it hits, and the workaround.
gh issue create --repo educlopez/friction-log --title "Friction: …" --label friction --body-file -
One issue per papercut. Omit secrets. Quote the relevant excerpt, not a
transcript.
